← previous blocknext block →recent activity
Analyzing
Block #87,349,211
12 transactions · 12 stateful · 2026-07-12 21:22:28 UTC
Parallelism
75/100
Blocked
17%
Avg conflicts / tx
0.17
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,349,211 · 12 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
5w07w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2f35c56f…046b
0x34b655…2a6f
4 touches
1 conflict
0xdf15e2bf…d7a9
0x34b655…2a6f
4 touches
1 conflict
0x0dd44476…ef40
0x34b655…2a6f
4 touches
1 conflict
0xf1c07b7e…c5f7
0x1efe02…37d6
2 touches
0 conflicts
0x002a0f9e…b33b
0xea1b8e…c5ec
2 touches
0 conflicts
0x1005f9aa…8bfc
0xea1b8e…c5ec
2 touches
0 conflicts
0x1005f9aa…8bfd
0xea1b8e…c5ec
2 touches
0 conflicts
0x1005f9aa…8bff
0xea1b8e…c5ec
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 0x2f35c56f7b…bd046b
Audit this contract →
← previous block·next block →recent activity