← previous blocknext block →recent activity
Analyzing
Block #86,658,314
23 transactions · 17 stateful · 2026-07-09 16:24:36 UTC
Parallelism
83/100
Blocked
29%
Avg conflicts / tx
0.26
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,658,314 · 23 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
1w02w17w08w110w011w112w215w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xf79df061…e005
0xe52b14…7230
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x09a15b10…2639
0x754704…b603
4 touches
1 conflict
0x5149ba0e…d954
0x754704…b603
4 touches
1 conflict
0x0b0c2e8d…c1b8
0xe52b14…7230
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
3 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity