← previous blocknext block →recent activity
Analyzing
Block #94,808,306
20 transactions · 19 stateful · 2026-08-10 15:14:46 UTC
Parallelism
70/100
Blocked
47%
Avg conflicts / tx
1.05
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #94,808,306 · 20 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
1w02w03w15w06w17w28w310w211w112w415w516w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa3a621f8…75a2
0x34b655…2a6f
10 touches
10 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
8 touches
6 conflicts
0xc6000ba5…8d65
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x154594d5…564e
0x34b655…2a6f
4 touches
1 conflict
0x18010dbb…6b25
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
10 conflicts on slot 0xa3a621f8f3…6975a2
Audit this contract →
← previous block·next block →recent activity