← previous blocknext block →recent activity
Analyzing
Block #86,359,793
16 transactions · 15 stateful · 2026-07-08 07:06:43 UTC
Parallelism
69/100
Blocked
40%
Avg conflicts / tx
0.56
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,359,793 · 16 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w26w07w38w29w415w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x851145…3f07
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x9da6e429…074d
0xa6afd3…d132
6 touches
3 conflicts
0xfc578b53…9b1f
0xa6afd3…d132
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0xd996735f…8730
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0xef65bff3…7c9d
0x2a68ba…90c5
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: 0x851145ea…9f3f07
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity