← previous blocknext block →recent activity
Analyzing
Block #87,304,184
20 transactions · 19 stateful · 2026-07-12 16:21:22 UTC
Parallelism
55/100
Blocked
53%
Avg conflicts / tx
0.95
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #87,304,184 · 20 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w16w27w38w49w513w517w618w719w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa05444cf…cd70
0x34b655…2a6f
8 touches
6 conflicts
0x805d08cf…3cfc
0x34b655…2a6f
6 touches
3 conflicts
0x9a2de05d…3e6b
0x34b655…2a6f
6 touches
3 conflicts
0x22fc9794…6e93
0x34b655…2a6f
6 touches
3 conflicts
0xcfb45859…3832
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0xa05444cff4…1ecd70
Audit this contract →
← previous block·next block →recent activity