← previous blocknext block →recent activity
Analyzing
Block #94,791,065
32 transactions · 30 stateful · 2026-08-10 13:48:03 UTC
Parallelism
81/100
Blocked
60%
Avg conflicts / tx
1.34
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #94,791,065 · 32 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w26w37w08w19w210w011w120w321w228w329w430w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x59dccbd8…2bf6
0x34b655…2a6f
12 touches
15 conflicts
0x0a57a2b8…3cdd
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001a
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002a
0x1b6862…e19c
8 touches
6 conflicts
0xc6a8c250…737b
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 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: Perpl
15 conflicts on slot 0x59dccbd857…c52bf6
Audit this contract →
← previous block·next block →recent activity