← previous blocknext block →recent activity

Analyzing

Block #72,370,641

12 transactions · 9 stateful · 2026-05-04 11:51:30 UTC

Parallelism

67/100

Blocked

33%

Avg conflicts / tx

0.33

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #72,370,641  ·  12 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others

Conflict graph

Blocked by

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0x2120af30…d2a9

0x065c9d…c394

5 touches
3 conflicts

0xc3c8642a…7da5

0x2a68ba…90c5

4 touches
1 conflict

0x6a1759aa…ef04

0xd32edf…ff58

3 touches
1 conflict

0x2fb6ddd2…b2a4

0x000000…012a

2 touches
0 conflicts

0x335a161d…fe7f

0x000000…012a

2 touches
0 conflicts

0x00000000…0013

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…0015

0x1b6862…e19c

2 touches
0 conflicts

0xba5743c7…21c1

0x1b6862…e19c

2 touches
0 conflicts

What's blocking what?

Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.

The bottleneck

Throughput-killer: 0x065c9d28…a9c394

3 conflicts on slot 0x2120af306f…54d2a9

← previous block·next block →recent activity