← previous blocknext block →recent activity
Analyzing
Block #87,616,111
16 transactions · 16 stateful · 2026-07-14 03:08:14 UTC
Parallelism
75/100
Blocked
38%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,616,111 · 16 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w05w18w111w112w215w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x540fe46f…a3d0
0x34b655…2a6f
6 touches
3 conflicts
0x2c53a187…3646
0x34b655…2a6f
6 touches
3 conflicts
0x25329a48…4e00
0x34b655…2a6f
4 touches
1 conflict
0x26054cbe…47df
0x34b655…2a6f
4 touches
1 conflict
0x2a513dfb…2bb8
0x34b655…2a6f
4 touches
1 conflict
0x6ac6d1bf…8b19
0x34b655…2a6f
4 touches
1 conflict
0x6dcb5d8d…5f07
0x34b655…2a6f
4 touches
1 conflict
0x6fca8941…b68b
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 0x540fe46fcc…70a3d0
Audit this contract →
← previous block·next block →recent activity