← previous blocknext block →recent activity
Analyzing
Block #86,635,327
21 transactions · 17 stateful · 2026-07-09 13:49:44 UTC
Parallelism
90/100
Blocked
18%
Avg conflicts / tx
0.19
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,635,327 · 21 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w05w07w117w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5fe7e126…6dd2
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x8a5ced1c…3b29
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x9733a466…1ea5
0xd32edf…ff58
3 touches
1 conflict
0x19cba3ac…9f15
0x34b655…2a6f
2 touches
0 conflicts
0x33018b40…8465
0x34b655…2a6f
2 touches
0 conflicts
0x3fa1fac4…826c
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0x5fe7e1267e…896dd2
Audit this contract →
← previous block·next block →recent activity