← previous blocknext block →recent activity
Analyzing
Block #87,496,680
24 transactions · 19 stateful · 2026-07-13 13:48:40 UTC
Parallelism
79/100
Blocked
32%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,496,680 · 24 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
1w02w13w011w013w116w221w222w323w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7b2f3e6d…978f
0x34b655…2a6f
6 touches
3 conflicts
0x4c188934…158e
0x34b655…2a6f
6 touches
3 conflicts
0xd5dbfacf…c5ec
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x15c9b5bf…f732
0x34b655…2a6f
4 touches
1 conflict
0x326d4924…1788
0x34b655…2a6f
4 touches
1 conflict
0x4ef263bb…fcf0
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 0x7b2f3e6d7d…4d978f
Audit this contract →
← previous block·next block →recent activity