← previous blocknext block →recent activity
Analyzing
Block #94,479,014
20 transactions · 19 stateful · 2026-08-09 11:37:03 UTC
Parallelism
90/100
Blocked
11%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #94,479,014 · 20 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w15w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6536722f…6b4e
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xcb21158b…f18d
0x34b655…2a6f
4 touches
1 conflict
0x1e137b39…bae2
0x34b655…2a6f
2 touches
0 conflicts
0x375b4ca6…52bb
0x34b655…2a6f
2 touches
0 conflicts
0x4e58f1d6…2fca
0x34b655…2a6f
2 touches
0 conflicts
0x69411fb3…e36d
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0x6536722f93…886b4e
Audit this contract →
← previous block·next block →recent activity