← previous blocknext block →recent activity
Analyzing
Block #86,817,063
20 transactions · 18 stateful · 2026-07-10 10:04:42 UTC
Parallelism
65/100
Blocked
50%
Avg conflicts / tx
0.65
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,817,063 · 20 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
1w02w03w04w15w28w39w410w511w113w114w619w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0x2328941c…84d3
0x34b655…2a6f
4 touches
1 conflict
0x30643e3a…dc6f
0x34b655…2a6f
4 touches
1 conflict
0x3ed62d2c…5852
0x34b655…2a6f
4 touches
1 conflict
0x4f4bdabd…ffba
0x34b655…2a6f
4 touches
1 conflict
0x55d5cc2c…4efa
0x34b655…2a6f
4 touches
1 conflict
0x725c0153…5f97
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
6 conflicts on slot 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity