← previous blocknext block →recent activity
Analyzing
Block #85,914,435
38 transactions · 29 stateful · 2026-07-06 05:33:32 UTC
Parallelism
82/100
Blocked
62%
Avg conflicts / tx
1.13
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #85,914,435 · 38 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
1w02w16w17w28w29w310w011w112w213w315w416w522w123w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x04fdea…47d7
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x5ec3614a…f22f
0xd32edf…ff58
7 touches
6 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x518f2037…e422
0xa6afd3…d132
6 touches
3 conflicts
0x66f473d3…2d03
0xa6afd3…d132
6 touches
3 conflicts
0x427c9fc4…5cee
0x34b655…2a6f
6 touches
3 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: 0x04fdeac2…f747d7
15 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity