← previous blocknext block →recent activity
Analyzing
Block #85,991,496
26 transactions · 21 stateful · 2026-07-06 14:07:45 UTC
Parallelism
77/100
Blocked
38%
Avg conflicts / tx
0.69
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #85,991,496 · 26 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
1w05w06w19w011w112w213w314w415w519w121w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x04fdea…47d7
12 touches
15 conflicts
0x00000000…000c
0x453805…c7fd
4 touches
1 conflict
0x12530975…a089
0x3bd359…433a
4 touches
1 conflict
0x00000000…0004
0x453805…c7fd
4 touches
1 conflict
0x9973417c…8ab4
0x754704…b603
4 touches
1 conflict
0x00000000…0000
0x453805…c7fd
4 touches
1 conflict
0x00000000…0002
0x453805…c7fd
4 touches
1 conflict
0x84a17857…cf35
0xd32edf…ff58
3 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: 0x04fdeac2…f747d7
15 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity