← previous blocknext block →recent activity
Analyzing
Block #93,572,844
24 transactions · 21 stateful · 2026-08-06 07:23:45 UTC
Parallelism
79/100
Blocked
38%
Avg conflicts / tx
0.58
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #93,572,844 · 24 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w06w17w08w09w110w211w112w316w422w023w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8218911e…3bed
0x34b655…2a6f
8 touches
6 conflicts
0x4e8c4408…d37b
0x34b655…2a6f
6 touches
3 conflicts
0x4e8c4408…d37a
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x5a19ef35…dc70
0x34b655…2a6f
4 touches
1 conflict
0xb1849477…ecff
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
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
6 conflicts on slot 0x8218911eb6…d93bed
Audit this contract →
← previous block·next block →recent activity