← previous blocknext block →recent activity
Analyzing
Block #87,341,712
13 transactions · 11 stateful · 2026-07-12 20:32:20 UTC
Parallelism
62/100
Blocked
55%
Avg conflicts / tx
0.69
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,341,712 · 13 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
1w02w13w24w25w36w37w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x37ee30c9…9e70
0x34b655…2a6f
8 touches
6 conflicts
0x0f15f74f…8d72
0x34b655…2a6f
4 touches
1 conflict
0x1737ef68…1e55
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x35d95fb0…db9e
0x34b655…2a6f
4 touches
1 conflict
0x35d95fb0…db9f
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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
6 conflicts on slot 0x37ee30c996…d19e70
Audit this contract →
← previous block·next block →recent activity