← previous blocknext block →recent activity
Analyzing
Block #96,600,379
26 transactions · 21 stateful · 2026-08-16 21:44:46 UTC
Parallelism
65/100
Blocked
57%
Avg conflicts / tx
1.77
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #96,600,379 · 26 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w36w19w410w514w615w718w719w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac2a0273…721b
0x34b655…2a6f
18 touches
36 conflicts
0x4acbdbcf…a8c6
0x34b655…2a6f
16 touches
28 conflicts
0x737acb78…fce8
0x34b655…2a6f
16 touches
28 conflicts
0x00000000…00c9
0x34b655…2a6f
10 touches
10 conflicts
0xfc8cd993…5c11
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…641f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 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
36 conflicts on slot 0xac2a02739b…81721b
Audit this contract →
← previous block·next block →recent activity