← previous blocknext block →recent activity
Analyzing
Block #94,796,409
13 transactions · 13 stateful · 2026-08-10 14:14:56 UTC
Parallelism
62/100
Blocked
31%
Avg conflicts / tx
0.77
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #94,796,409 · 13 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
2w03w14w26w07w311w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcb578d94…6e0d
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x4188cc5f…2d2e
0x34b655…2a6f
4 touches
1 conflict
0x46ee3c65…4ab8
0x34b655…2a6f
4 touches
1 conflict
0xf15273a1…2c52
0x34b655…2a6f
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x000bde1a…e123
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
6 conflicts on slot 0xcb578d94e3…1d6e0d
Audit this contract →
← previous block·next block →recent activity