← previous blocknext block →recent activity
Analyzing
Block #93,560,325
15 transactions · 13 stateful · 2026-08-06 06:20:50 UTC
Parallelism
73/100
Blocked
38%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #93,560,325 · 15 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w06w17w08w19w210w011w112w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb8fe8310…4bd5
0x34b655…2a6f
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x3dae5ee1…721b
0x34b655…2a6f
4 touches
1 conflict
0x5a91d45c…19fa
0x34b655…2a6f
4 touches
1 conflict
0x953517cb…cdec
0x34b655…2a6f
4 touches
1 conflict
0xa35509fa…5cb3
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…641f
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
3 conflicts on slot 0xb8fe831098…0e4bd5
Audit this contract →
← previous block·next block →recent activity