← previous blocknext block →recent activity
Analyzing
Block #87,626,116
19 transactions · 19 stateful · 2026-07-14 04:15:07 UTC
Parallelism
79/100
Blocked
16%
Avg conflicts / tx
0.21
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,626,116 · 19 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
6w07w18w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x008accc4…1da7
0x34b655…2a6f
4 touches
1 conflict
0x02fabc35…2769
0x34b655…2a6f
4 touches
1 conflict
0x06e5a219…0057
0x34b655…2a6f
4 touches
1 conflict
0x06e5a219…0058
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x312235a6…7b85
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x48b8d2e5…3f2f
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 0x008accc476…b51da7
Audit this contract →
← previous block·next block →recent activity