← previous blocknext block →recent activity
Analyzing
Block #87,783,972
16 transactions · 15 stateful · 2026-07-14 21:51:03 UTC
Parallelism
88/100
Blocked
27%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,783,972 · 16 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w18w19w010w114w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1df9644f…d014
0x34b655…2a6f
4 touches
1 conflict
0x3347cbe5…846c
0x34b655…2a6f
4 touches
1 conflict
0x40a9339c…6571
0x34b655…2a6f
4 touches
1 conflict
0x40a9339c…6572
0x34b655…2a6f
4 touches
1 conflict
0x7138c945…f6a8
0x34b655…2a6f
4 touches
1 conflict
0x791fbe1d…ac3c
0x34b655…2a6f
4 touches
1 conflict
0x828d7de6…9a15
0x34b655…2a6f
4 touches
1 conflict
0xa5deef6f…6c3f
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 0x1df9644ff6…c9d014
Audit this contract →
← previous block·next block →recent activity