← previous blocknext block →recent activity
Analyzing
Block #87,627,866
13 transactions · 12 stateful · 2026-07-14 04:26:51 UTC
Parallelism
85/100
Blocked
8%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,627,866 · 13 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
2w04w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x536588d3…19c5
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0xc36fa358…24cb
0x34b655…2a6f
4 touches
1 conflict
0xef1cbbb7…8cc8
0x34b655…2a6f
4 touches
1 conflict
0x04699d57…22e8
0x34b655…2a6f
2 touches
0 conflicts
0x04f4909f…6357
0x34b655…2a6f
2 touches
0 conflicts
0x07f69062…03ec
0x34b655…2a6f
2 touches
0 conflicts
0x0dcb313d…7073
0x34b655…2a6f
2 touches
0 conflicts
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 0x536588d3d7…2719c5
Audit this contract →
← previous block·next block →recent activity