← previous blocknext block →recent activity
Analyzing
Block #87,587,612
9 transactions · 6 stateful · 2026-07-13 23:57:37 UTC
Parallelism
78/100
Blocked
33%
Avg conflicts / tx
0.22
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,587,612 · 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
1w02w14w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc56d6548…50a4
0x34b655…2a6f
4 touches
1 conflict
0xd5e6e5ee…9fb2
0x34b655…2a6f
4 touches
1 conflict
0xd64c1971…1bf2
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x53355553…2976
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 0xc56d654866…5050a4
Audit this contract →
← previous block·next block →recent activity