← previous blocknext block →recent activity
Analyzing
Block #94,793,590
71 transactions · 57 stateful · 2026-08-10 14:00:45 UTC
Parallelism
70/100
Blocked
79%
Avg conflicts / tx
3.1
Longest chain
21 deep
Execution timeline
did this block parallelize well?
view
block #94,793,590 · 71 txs across 21 waves · depth 21
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
wave w17
wave w18
wave w19
wave w20
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w415w516w617w724w857w858w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc6000ba5…8d65
0x34b655…2a6f
18 touches
36 conflicts
0xa35c15b8…e0bf
0xd32edf…ff58
17 touches
36 conflicts
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0x2840c278…bbc7
0x34b655…2a6f
16 touches
28 conflicts
0x2741f63d…a456
0x34b655…2a6f
14 touches
21 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
12 touches
15 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
12 touches
15 conflicts
0xca841faa…486a
0x34b655…2a6f
12 touches
15 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
36 conflicts on slot 0xc6000ba5c1…988d65
Audit this contract →
← previous block·next block →recent activity