← previous blocknext block →recent activity
Analyzing
Block #86,696,175
19 transactions · 16 stateful · 2026-07-09 20:37:13 UTC
Parallelism
63/100
Blocked
56%
Avg conflicts / tx
1.37
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,696,175 · 19 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w36w48w59w615w417w518w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
14 touches
21 conflicts
0x92385428…6941
0x34b655…2a6f
12 touches
15 conflicts
0xd1952ceb…56be
0x34b655…2a6f
10 touches
10 conflicts
0x01df0928…3426
0x34b655…2a6f
6 touches
3 conflicts
0x01df0928…3427
0x34b655…2a6f
6 touches
3 conflicts
0x0b320394…cc69
0x34b655…2a6f
6 touches
3 conflicts
0x89c7ec3b…85ba
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 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
21 conflicts on slot 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity