← previous blocknext block →recent activity
Analyzing
Block #85,334,504
28 transactions · 16 stateful · 2026-07-03 13:10:19 UTC
Parallelism
86/100
Blocked
31%
Avg conflicts / tx
0.18
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,334,504 · 28 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w010w114w016w121w223w127w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x06e7db76…ef34
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
0x5540f956…69e8
0x065c9d…c394
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x2bf5914f…c75d
0x34b655…2a6f
4 touches
1 conflict
0x69444a89…71f6
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: Perpl
1 conflict on slot 0x06e7db765f…d5ef34
Audit this contract →
← previous block·next block →recent activity