← previous blocknext block →recent activity
Analyzing
Block #85,828,584
21 transactions · 20 stateful · 2026-07-05 20:01:38 UTC
Parallelism
52/100
Blocked
65%
Avg conflicts / tx
2.38
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #85,828,584 · 21 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w26w37w48w59w610w711w812w913w215w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…000a
0x90c374…be45
20 touches
45 conflicts
0x00000000…000b
0x90c374…be45
20 touches
45 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001f
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002f
0x1b6862…e19c
4 touches
1 conflict
0xd25997d0…a68a
0x1b6862…e19c
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: 0x90c3747c…0ebe45
45 conflicts on slot 0x0000000000…00000a
Audit this contract →
← previous block·next block →recent activity