← previous blocknext block →recent activity
Analyzing
Block #86,772,832
19 transactions · 17 stateful · 2026-07-10 05:09:21 UTC
Parallelism
74/100
Blocked
29%
Avg conflicts / tx
0.53
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,772,832 · 19 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
1w03w05w18w19w211w316w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x737acb78…fce8
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0x5382ffe1…f904
0x34b655…2a6f
4 touches
1 conflict
0x6b899aa5…a7a6
0x34b655…2a6f
4 touches
1 conflict
0x74550a4b…68bd
0x34b655…2a6f
4 touches
1 conflict
0x778a3faa…441b
0x34b655…2a6f
4 touches
1 conflict
0x778a3faa…441c
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 0x737acb7813…fafce8
Audit this contract →
← previous block·next block →recent activity