← previous blocknext block →recent activity
Analyzing
Block #93,185,481
23 transactions · 23 stateful · 2026-08-04 22:56:18 UTC
Parallelism
57/100
Blocked
57%
Avg conflicts / tx
1.83
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #93,185,481 · 23 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w15w26w37w48w59w613w717w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x737acb78…fce8
0x34b655…2a6f
14 touches
21 conflicts
0xbde524f4…43bf
0x34b655…2a6f
14 touches
21 conflicts
0xac2a0273…721b
0x34b655…2a6f
12 touches
15 conflicts
0xce06a0f7…efef
0x34b655…2a6f
11 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x738b798d…00f1
0x34b655…2a6f
7 touches
6 conflicts
0xcdb40908…3ccd
0x34b655…2a6f
7 touches
6 conflicts
0xbcbf5d09…8bac
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
21 conflicts on slot 0x737acb7813…fafce8
Audit this contract →
← previous block·next block →recent activity