← previous blocknext block →recent activity
Analyzing
Block #85,744,388
26 transactions · 19 stateful · 2026-07-05 10:41:01 UTC
Parallelism
88/100
Blocked
37%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,744,388 · 26 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w06w17w28w217w224w125w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb8fccd1b…b5f2
0x69df8a…6292
6 touches
3 conflicts
0xb68e226d…c054
0xa6afd3…d132
6 touches
3 conflicts
0x0d622e34…0000
0x681e90…ae09
6 touches
3 conflicts
0xdf708ee7…1fcf
0xc8689a…ee79
6 touches
3 conflicts
0x55012d1a…3907
0x69df8a…6292
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xa1ac5db0…43c7
0xd32edf…ff58
5 touches
3 conflicts
0x40970e69…da50
0x69df8a…6292
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: 0x69df8a43…506292
3 conflicts on slot 0xb8fccd1bf0…d6b5f2
Audit this contract →
← previous block·next block →recent activity