← previous blocknext block →recent activity
Analyzing
Block #93,349,628
20 transactions · 19 stateful · 2026-08-05 12:41:34 UTC
Parallelism
55/100
Blocked
58%
Avg conflicts / tx
1.45
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #93,349,628 · 20 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w36w47w510w411w513w616w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x808129fc…f97d
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0xd66696e0…0842
0x34b655…2a6f
8 touches
6 conflicts
0x9930958d…b7dd
0x34b655…2a6f
8 touches
6 conflicts
0x948836ff…59ab
0x34b655…2a6f
6 touches
3 conflicts
0xa64c2112…1c65
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
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 0x808129fc27…daf97d
Audit this contract →
← previous block·next block →recent activity