← previous blocknext block →recent activity
Analyzing
Block #72,301,847
9 transactions · 6 stateful · 2026-05-04 04:13:16 UTC
Parallelism
78/100
Blocked
17%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #72,301,847 · 9 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
6w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x207c32d3…d39b
0x34b655…2a6f
4 touches
1 conflict
0x7cbd466f…1700
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xf853eb8e…4027
0x34b655…2a6f
4 touches
1 conflict
0x01670cd7…eeaf
0x065c9d…c394
2 touches
0 conflicts
0x88b246fc…d7c6
0x065c9d…c394
2 touches
0 conflicts
0xd809aa9e…6807
0x065c9d…c394
2 touches
0 conflicts
0xef9a0989…526f
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 0x207c32d3f0…39d39b
Audit this contract →
← previous block·next block →recent activity