← previous blocknext block →recent activity
Analyzing
Block #86,735,092
16 transactions · 15 stateful · 2026-07-10 00:57:07 UTC
Parallelism
63/100
Blocked
47%
Avg conflicts / tx
0.81
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,735,092 · 16 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w07w18w29w311w413w414w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0xa08f40b2…9a93
0x34b655…2a6f
6 touches
3 conflicts
0x0bc5d643…38d9
0x34b655…2a6f
4 touches
1 conflict
0x1ffe7d94…61ea
0x34b655…2a6f
4 touches
1 conflict
0x4c7b72e8…9a1f
0x34b655…2a6f
4 touches
1 conflict
0x61757a59…d89f
0x34b655…2a6f
4 touches
1 conflict
0x6323c5ea…ce8a
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
10 conflicts on slot 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity