← previous blocknext block →recent activity
Analyzing
Block #87,661,530
23 transactions · 18 stateful · 2026-07-14 08:11:46 UTC
Parallelism
78/100
Blocked
33%
Avg conflicts / tx
0.3
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,661,530 · 23 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
2w03w16w011w215w316w017w119w322w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xee28d8b5…bd37
0x34b655…2a6f
4 touches
1 conflict
0x8bf661cb…bcd2
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xc514314c…1aa4
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x0a6c31fc…f4c3
0x34b655…2a6f
4 touches
1 conflict
0x560b6fd9…a104
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 0xee28d8b544…a8bd37
Audit this contract →
← previous block·next block →recent activity