← previous blocknext block →recent activity
Analyzing
Block #93,456,238
28 transactions · 26 stateful · 2026-08-05 21:37:35 UTC
Parallelism
71/100
Blocked
50%
Avg conflicts / tx
1.21
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #93,456,238 · 28 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
1w02w13w06w17w28w39w410w519w621w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9ba6ae4a…90cb
0x34b655…2a6f
14 touches
21 conflicts
0x482471ad…122f
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6426
0x34b655…2a6f
12 touches
15 conflicts
0xe516e427…f995
0x34b655…2a6f
10 touches
10 conflicts
0xf60db55a…a155
0x34b655…2a6f
6 touches
3 conflicts
0x5060cdde…445d
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 0x9ba6ae4a28…c990cb
Audit this contract →
← previous block·next block →recent activity