← previous blocknext block →recent activity
Analyzing
Block #85,519,283
17 transactions · 14 stateful · 2026-07-04 09:40:47 UTC
Parallelism
65/100
Blocked
43%
Avg conflicts / tx
0.94
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #85,519,283 · 17 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
5w06w17w28w39w410w514w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0b0c2e8d…c1b8
0xe52b14…7230
12 touches
15 conflicts
0x09a15b10…2639
0x754704…b603
12 touches
15 conflicts
0x5149ba0e…d954
0x754704…b603
12 touches
15 conflicts
0xf79df061…e005
0xe52b14…7230
12 touches
15 conflicts
0x532023a5…d800
0xe52b14…7230
12 touches
15 conflicts
0x8ffa3328…ce11
0xe52b14…7230
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xa8c7f78e…5815
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: 0xe52b1424…bb7230
15 conflicts on slot 0x0b0c2e8d5e…dbc1b8
Audit this contract →
← previous block·next block →recent activity