← previous blocknext block →recent activity
Analyzing
Block #72,395,289
9 transactions · 7 stateful · 2026-05-04 14:35:48 UTC
Parallelism
67/100
Blocked
43%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #72,395,289 · 9 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
1w02w15w27w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbfca3cd0…5023
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x5dad856a…a46d
0xd32edf…ff58
3 touches
1 conflict
0x08934307…fcc3
0x065c9d…c394
2 touches
0 conflicts
0x105ed58f…f3a4
0x065c9d…c394
2 touches
0 conflicts
0x5ff611d5…b6cd
0x065c9d…c394
2 touches
0 conflicts
0x7c842180…1b7b
0x065c9d…c394
2 touches
0 conflicts
0x9e972fda…f4a6
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: Perpl
1 conflict on slot 0xbfca3cd067…cd5023
Audit this contract →
← previous block·next block →recent activity