← previous blocknext block →recent activity
Analyzing
Block #72,570,954
11 transactions · 8 stateful · 2026-05-05 10:05:40 UTC
Parallelism
73/100
Blocked
25%
Avg conflicts / tx
0.27
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #72,570,954 · 11 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w15w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x36628532…fd55
0x065c9d…c394
6 touches
3 conflicts
0xa4d48640…3d4b
0x065c9d…c394
5 touches
3 conflicts
0x30563bd8…1af3
0x065c9d…c394
4 touches
1 conflict
0xf17777e5…0950
0x065c9d…c394
3 touches
1 conflict
0x8b8fb1ae…a78f
0x065c9d…c394
3 touches
1 conflict
0xdf95bb39…20a7
0x065c9d…c394
3 touches
1 conflict
0x0df23082…df9e
0x065c9d…c394
3 touches
1 conflict
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: Kuru Exchange: Market-MON/USDC
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity