← previous blocknext block →recent activity
Analyzing
Block #94,839,482
30 transactions · 20 stateful · 2026-08-10 17:51:37 UTC
Parallelism
83/100
Blocked
60%
Avg conflicts / tx
0.77
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #94,839,482 · 30 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w27w39w010w111w212w313w124w425w226w327w428w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x40c49f…2af0
8 touches
6 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0x76d1e78d…7877
0x40c49f…2af0
6 touches
3 conflicts
0x4b598505…7d1f
0x40c49f…2af0
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x5d46e6a0…5ed9
0x40c49f…2af0
6 touches
3 conflicts
0x261cbea7…e35d
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: 0x40c49f17…d22af0
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity