← previous blocknext block →recent activity
Analyzing
Block #86,926,300
13 transactions · 11 stateful · 2026-07-10 22:15:13 UTC
Parallelism
85/100
Blocked
18%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,926,300 · 13 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
4w06w07w110w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4b5d1fb9…a439
0x5b09b6…a607
4 touches
1 conflict
0x4b5d1fb9…a43b
0x5b09b6…a607
4 touches
1 conflict
0xad676684…c58b
0x754704…b603
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0006
0x5b09b6…a607
4 touches
1 conflict
0x4b5d1fb9…a435
0x5b09b6…a607
4 touches
1 conflict
0x4b5d1fb9…a436
0x5b09b6…a607
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
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: 0x5b09b68b…c6a607
1 conflict on slot 0x4b5d1fb910…1aa439
Audit this contract →
← previous block·next block →recent activity