← previous blocknext block →recent activity
Analyzing
Block #94,697,130
49 transactions · 43 stateful · 2026-08-10 05:54:05 UTC
Parallelism
61/100
Blocked
79%
Avg conflicts / tx
2.73
Longest chain
19 deep
Execution timeline
did this block parallelize well?
view
block #94,697,130 · 49 txs across 19 waves · depth 19
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w26w37w09w011w112w213w215w316w417w520w828w1036w137w338w439w444w1645w1746w18
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4f1ad4b4…e00a
0x34b655…2a6f
16 touches
28 conflicts
0xec7d120d…7084
0x34b655…2a6f
16 touches
28 conflicts
0xbf78ee7f…e7fd
0x34b655…2a6f
12 touches
15 conflicts
0xca841faa…486a
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…0002
0xeae24c…0be0
10 touches
10 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
8 touches
6 conflicts
0x093ed178…3946
0x34b655…2a6f
8 touches
6 conflicts
0x53699236…fede
0x34b655…2a6f
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
28 conflicts on slot 0x4f1ad4b4ec…b9e00a
Audit this contract →
← previous block·next block →recent activity