← previous blocknext block →recent activity
Analyzing
Block #94,912,916
24 transactions · 22 stateful · 2026-08-11 00:00:58 UTC
Parallelism
67/100
Blocked
55%
Avg conflicts / tx
1.54
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #94,912,916 · 24 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w47w58w59w614w615w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0x482471ad…122f
0x34b655…2a6f
14 touches
21 conflicts
0xb39cb1d8…effa
0x34b655…2a6f
10 touches
10 conflicts
0xea02471d…1542
0x34b655…2a6f
8 touches
6 conflicts
0xbda6c72f…2a3c
0x34b655…2a6f
8 touches
6 conflicts
0x1d9867ad…6d9a
0x34b655…2a6f
6 touches
3 conflicts
0xb1482428…45f3
0x34b655…2a6f
6 touches
3 conflicts
0xbde524f4…43bf
0x34b655…2a6f
6 touches
3 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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity