← previous blocknext block →recent activity
Analyzing
Block #87,325,452
12 transactions · 11 stateful · 2026-07-12 18:43:38 UTC
Parallelism
58/100
Blocked
55%
Avg conflicts / tx
0.75
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,325,452 · 12 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w06w17w28w29w311w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc36fa358…24cb
0x34b655…2a6f
6 touches
3 conflicts
0x0dfda697…1648
0x34b655…2a6f
4 touches
1 conflict
0x10ae525c…1c0f
0x34b655…2a6f
4 touches
1 conflict
0x259ed0cc…bef9
0x34b655…2a6f
4 touches
1 conflict
0x259ed0cc…befa
0x34b655…2a6f
4 touches
1 conflict
0x51b881db…7f40
0x34b655…2a6f
4 touches
1 conflict
0x79b71b8f…d775
0x34b655…2a6f
4 touches
1 conflict
0x7aad02c6…b979
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