← previous blocknext block →recent activity
Analyzing
Block #87,251,572
14 transactions · 12 stateful · 2026-07-12 10:29:35 UTC
Parallelism
71/100
Blocked
42%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,251,572 · 14 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
2w03w14w26w08w39w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6c68ddc9…d106
0xb1dbf0…c0d3
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x8a35acfb…d1ac
0xb1dbf0…c0d3
6 touches
3 conflicts
0x8a35acfb…d1ad
0xb1dbf0…c0d3
5 touches
3 conflicts
0x6999e902…ec56
0x34b655…2a6f
4 touches
1 conflict
0xa3abf9fa…6088
0x34b655…2a6f
4 touches
1 conflict
0xb6d174f3…e371
0x34b655…2a6f
4 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: 0xb1dbf05f…b1c0d3
3 conflicts on slot 0x6c68ddc9e3…b0d106
Audit this contract →
← previous block·next block →recent activity