← previous blocknext block →recent activity
Analyzing
Block #72,426,232
16 transactions · 11 stateful · 2026-05-04 18:02:03 UTC
Parallelism
88/100
Blocked
18%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #72,426,232 · 16 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w16w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0xc857141c…7218
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x905a7e01…fab7
0x065c9d…c394
3 touches
1 conflict
0xa8a560aa…a7be
0x065c9d…c394
3 touches
1 conflict
0x31e9ff2a…7dba
0x065c9d…c394
2 touches
0 conflicts
0x3414f9b0…771f
0x065c9d…c394
2 touches
0 conflicts
0x7d25b4ea…b468
0x065c9d…c394
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: 0x681e908b…e1ae09
1 conflict on slot 0x0d622e34f9…000000
Audit this contract →
← previous block·next block →recent activity