← previous blocknext block →recent activity
Analyzing
Block #86,045,834
23 transactions · 19 stateful · 2026-07-06 20:10:52 UTC
Parallelism
74/100
Blocked
53%
Avg conflicts / tx
0.52
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,045,834 · 23 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
1w02w13w14w26w17w38w413w014w118w519w121w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac33ff75…077b
0xfa32f9…f3f0
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x99f666e3…b2a2
0x3bd359…433a
6 touches
3 conflicts
0x9194f4a3…10b8
0x754704…b603
6 touches
3 conflicts
0x00000000…0001
0xfa32f9…f3f0
6 touches
3 conflicts
0x00000000…0000
0xfa32f9…f3f0
6 touches
3 conflicts
0x09500602…94e9
0x34b655…2a6f
4 touches
1 conflict
0x09500602…94ea
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: 0xfa32f9ec…fef3f0
3 conflicts on slot 0xac33ff75c1…89077b
Audit this contract →
← previous block·next block →recent activity