← previous blocknext block →recent activity
Analyzing
Block #96,652,214
26 transactions · 26 stateful · 2026-08-17 02:05:29 UTC
Parallelism
62/100
Blocked
58%
Avg conflicts / tx
2.04
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #96,652,214 · 26 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w15w26w27w39w315w416w517w618w723w724w825w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4c188934…158e
0x34b655…2a6f
14 touches
21 conflicts
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0xf9e6fb7f…9bf1
0x34b655…2a6f
10 touches
10 conflicts
0x745952b2…d90c
0x34b655…2a6f
10 touches
10 conflicts
0x67708716…f9b6
0x34b655…2a6f
8 touches
6 conflicts
0xaba6578d…bd48
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x3ed49969…0ed7
0x34b655…2a6f
6 touches
3 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
21 conflicts on slot 0x4c18893450…c5158e
Audit this contract →
← previous block·next block →recent activity