← previous blocknext block →recent activity
Analyzing
Block #93,674,903
18 transactions · 17 stateful · 2026-08-06 15:56:50 UTC
Parallelism
67/100
Blocked
53%
Avg conflicts / tx
1.61
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #93,674,903 · 18 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w25w36w17w28w313w414w517w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…00c9
0x34b655…2a6f
10 touches
10 conflicts
0x3f2cf0ae…a94b
0x34b655…2a6f
10 touches
10 conflicts
0x6822a8aa…667f
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…641f
0x34b655…2a6f
10 touches
10 conflicts
0xf1a88c62…4747
0x34b655…2a6f
10 touches
10 conflicts
0xf5f815e7…c83e
0x34b655…2a6f
10 touches
10 conflicts
0xc6000ba5…8d65
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 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 0x0000000000…0000c9
Audit this contract →
← previous block·next block →recent activity