← previous blocknext block →recent activity
Analyzing
Block #87,318,589
10 transactions · 9 stateful · 2026-07-12 17:57:42 UTC
Parallelism
70/100
Blocked
33%
Avg conflicts / tx
0.3
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,318,589 · 10 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
2w04w05w16w27w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc5f336ca…912e
0x34b655…2a6f
4 touches
1 conflict
0x4fdbc928…4a1f
0x34b655…2a6f
4 touches
1 conflict
0x4fdbc928…4a20
0x34b655…2a6f
4 touches
1 conflict
0x6e1cd42e…1f23
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x80fd3987…2314
0x34b655…2a6f
4 touches
1 conflict
0x8bc75e93…089f
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
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
1 conflict on slot 0xc5f336cacf…d3912e
Audit this contract →
← previous block·next block →recent activity