← previous blocknext block →recent activity
Analyzing
Block #96,640,028
26 transactions · 22 stateful · 2026-08-17 01:04:11 UTC
Parallelism
81/100
Blocked
41%
Avg conflicts / tx
0.73
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #96,640,028 · 26 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
2w03w15w06w17w08w112w013w116w019w120w223w224w325w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x529e53cf…38e4
0xa6afd3…d132
6 touches
3 conflicts
0x66d5e476…8a1f
0x34b655…2a6f
6 touches
3 conflicts
0x989252a1…d812
0xa6afd3…d132
6 touches
3 conflicts
0x745952b2…d90c
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
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
6 conflicts on slot 0xac2a02739b…81721b
Audit this contract →
← previous block·next block →recent activity