← previous blocknext block →recent activity
Analyzing
Block #94,686,566
22 transactions · 22 stateful · 2026-08-10 05:00:58 UTC
Parallelism
77/100
Blocked
50%
Avg conflicts / tx
1.18
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #94,686,566 · 22 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
1w02w13w24w35w06w17w08w19w210w311w413w016w217w321w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0x217bd767…b79e
0x34b655…2a6f
8 touches
6 conflicts
0x3c73dc67…0e78
0xd32edf…ff58
7 touches
6 conflicts
0xecb4264b…7cf9
0x34b655…2a6f
6 touches
3 conflicts
0xc08384da…ecb7
0x34b655…2a6f
6 touches
3 conflicts
0x4979282b…2931
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x03da5c00…b353
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
10 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity