← previous blocknext block →recent activity
Analyzing
Block #87,610,245
20 transactions · 13 stateful · 2026-07-14 02:29:00 UTC
Parallelism
85/100
Blocked
38%
Avg conflicts / tx
0.3
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,610,245 · 20 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
2w03w07w19w110w012w118w119w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x17c70f19…23a7
0x34b655…2a6f
4 touches
1 conflict
0x1ee4a6d2…6389
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x3bd78506…1f86
0x34b655…2a6f
4 touches
1 conflict
0x6aa1497c…2292
0x34b655…2a6f
4 touches
1 conflict
0x7527802e…2ba9
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xd7fe05cd…207e
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 0x17c70f1948…0f23a7
Audit this contract →
← previous block·next block →recent activity