← previous blocknext block →recent activity
Analyzing
Block #93,500,730
33 transactions · 29 stateful · 2026-08-06 01:21:15 UTC
Parallelism
76/100
Blocked
38%
Avg conflicts / tx
0.88
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #93,500,730 · 33 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
2w04w15w26w37w410w111w412w513w614w518w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x54391ab3…c33b
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xe3da81f8…f96c
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
0x82bd9f0b…8289
0x34b655…2a6f
6 touches
3 conflicts
0x2c7d4036…04db
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
10 conflicts on slot 0x54391ab3c2…0dc33b
Audit this contract →
← previous block·next block →recent activity