← previous blocknext block →recent activity
Analyzing
Block #94,758,554
17 transactions · 16 stateful · 2026-08-10 11:04:31 UTC
Parallelism
82/100
Blocked
19%
Avg conflicts / tx
0.18
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #94,758,554 · 17 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w212w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x90a66fa7…9014
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x6459805c…615d
0x34b655…2a6f
4 touches
1 conflict
0xa527ea56…0c69
0x34b655…2a6f
4 touches
1 conflict
0x3643741b…109c
0x34b655…2a6f
2 touches
0 conflicts
0x3e06ff9a…7489
0x34b655…2a6f
2 touches
0 conflicts
0x4e9b892b…6877
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 0x90a66fa7d4…cf9014
Audit this contract →
← previous block·next block →recent activity