← previous blocknext block →recent activity
Analyzing
Block #86,611,846
17 transactions · 17 stateful · 2026-07-09 11:12:53 UTC
Parallelism
82/100
Blocked
41%
Avg conflicts / tx
0.47
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,611,846 · 17 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w15w06w17w210w111w015w116w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x76d36fa4…aaf6
0x34b655…2a6f
4 touches
1 conflict
0xfc578b53…9b1f
0xa6afd3…d132
4 touches
1 conflict
0x9da6e429…074d
0xa6afd3…d132
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0xfaef08b1…0696
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x89c7ec3b…85ba
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 0x76d36fa4cb…8faaf6
Audit this contract →
← previous block·next block →recent activity