← previous blocknext block →recent activity
Analyzing
Block #85,929,108
23 transactions · 18 stateful · 2026-07-06 07:11:16 UTC
Parallelism
78/100
Blocked
33%
Avg conflicts / tx
0.48
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,929,108 · 23 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w26w09w114w220w321w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x427c9fc4…5cee
0x34b655…2a6f
8 touches
6 conflicts
0x10a2bd5d…ad6d
0x8d1565…6723
6 touches
3 conflicts
0xc88f593e…5d93
0x336ed4…c59c
6 touches
3 conflicts
0x00000000…000b
0x90c374…be45
6 touches
3 conflicts
0x79250c04…e936
0x8d1565…6723
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…000a
0x90c374…be45
6 touches
3 conflicts
0xb3fb9fb5…64dc
0x34b655…2a6f
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: Perpl
6 conflicts on slot 0x427c9fc46b…895cee
Audit this contract →
← previous block·next block →recent activity