← previous blocknext block →recent activity
Analyzing
Block #95,799,589
16 transactions · 15 stateful · 2026-08-14 02:36:13 UTC
Parallelism
63/100
Blocked
40%
Avg conflicts / tx
0.81
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #95,799,589 · 16 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w15w26w07w18w311w413w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe26aee7b…f52b
0x34b655…2a6f
6 touches
3 conflicts
0x3c78ca04…432c
0x34b655…2a6f
6 touches
3 conflicts
0xe8eae8a3…bacc
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xd6313d73…483f
0x34b655…2a6f
6 touches
3 conflicts
0x36a76bd2…1fb0
0x34b655…2a6f
4 touches
1 conflict
0x5b30a6e6…b249
0x34b655…2a6f
4 touches
1 conflict
0x7aad02c6…b979
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
3 conflicts on slot 0xe26aee7b78…9ff52b
Audit this contract →
← previous block·next block →recent activity