← previous blocknext block →recent activity
Analyzing
Block #87,347,333
11 transactions · 10 stateful · 2026-07-12 21:09:54 UTC
Parallelism
73/100
Blocked
20%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,347,333 · 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
4w05w06w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc36fa358…24cb
0x34b655…2a6f
6 touches
3 conflicts
0xb6629430…e116
0x34b655…2a6f
4 touches
1 conflict
0xb7dbe79a…4499
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xf29e5320…ce2d
0x34b655…2a6f
4 touches
1 conflict
0x35d95fb0…db9f
0x34b655…2a6f
4 touches
1 conflict
0x35d95fb0…db9e
0x34b655…2a6f
4 touches
1 conflict
0x94ba9c4a…41d8
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: Perpl
3 conflicts on slot 0xc36fa35805…6f24cb
Audit this contract →
← previous block·next block →recent activity