← previous blocknext block →recent activity
Analyzing
Block #93,185,232
27 transactions · 27 stateful · 2026-08-04 22:55:03 UTC
Parallelism
63/100
Blocked
52%
Avg conflicts / tx
1.63
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #93,185,232 · 27 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
2w03w14w25w36w47w58w69w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbde524f4…43bf
0x34b655…2a6f
16 touches
28 conflicts
0x5b3e008a…4aa9
0x34b655…2a6f
12 touches
15 conflicts
0x737acb78…fce8
0x34b655…2a6f
12 touches
15 conflicts
0xac2a0273…721b
0x34b655…2a6f
12 touches
15 conflicts
0xce06a0f7…efef
0x34b655…2a6f
11 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x033cf007…136d
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 0xbde524f475…b143bf
Audit this contract →
← previous block·next block →recent activity