← previous blocknext block →recent activity
Analyzing
Block #85,676,132
14 transactions · 12 stateful · 2026-07-05 03:05:08 UTC
Parallelism
64/100
Blocked
42%
Avg conflicts / tx
0.79
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,676,132 · 14 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
1w02w13w24w35w49w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfc111d09…525a
0x336ed4…c59c
10 touches
10 conflicts
0x655939a8…0b3b
0x336ed4…c59c
10 touches
10 conflicts
0x00000000…000a
0x90c374…be45
10 touches
10 conflicts
0x00000000…000b
0x90c374…be45
10 touches
10 conflicts
0x659bf1d4…2024
0x336ed4…c59c
9 touches
10 conflicts
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x0c9eb6ea…7c39
0x34b655…2a6f
2 touches
0 conflicts
0x09000000…0001
0x000000…1000
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: 0x336ed437…cfc59c
10 conflicts on slot 0xfc111d09a6…d6525a
Audit this contract →
← previous block·next block →recent activity