← previous blocknext block →recent activity
Analyzing
Block #94,485,499
18 transactions · 16 stateful · 2026-08-09 12:09:40 UTC
Parallelism
61/100
Blocked
69%
Avg conflicts / tx
1.33
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #94,485,499 · 18 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w07w48w19w211w313w414w517w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8fe37a3f…4c89
0x34b655…2a6f
10 touches
10 conflicts
0xb0192d77…9f66
0xd32edf…ff58
9 touches
10 conflicts
0x11258774…9892
0x2a68ba…90c5
6 touches
3 conflicts
0x3d5788f0…1cb8
0x065c9d…c394
6 touches
3 conflicts
0x7aad02c6…b979
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x00000000…002c
0x1b6862…e19c
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 0x8fe37a3f4a…bf4c89
Audit this contract →
← previous block·next block →recent activity