← previous blocknext block →recent activity
Analyzing
Block #94,790,596
66 transactions · 50 stateful · 2026-08-10 13:45:41 UTC
Parallelism
74/100
Blocked
76%
Avg conflicts / tx
2.35
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #94,790,596 · 66 txs across 17 waves · depth 17
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w111w012w013w114w215w316w217w419w521w623w724w825w926w1037w343w447w248w149w1451w352w457w15
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb3fb9fb5…64db
0x34b655…2a6f
18 touches
36 conflicts
0x00000000…0002
0xeae24c…0be0
14 touches
21 conflicts
0x00000000…00c9
0x34b655…2a6f
12 touches
15 conflicts
0x95c47f03…f1bb
0x34b655…2a6f
12 touches
15 conflicts
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0x890a1db9…1712
0xa6afd3…d132
10 touches
10 conflicts
0x428b6e5b…8909
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…003d
0xa6afd3…d132
10 touches
10 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 0xb3fb9fb561…7664db
Audit this contract →
← previous block·next block →recent activity