← previous blocknext block →recent activity
Analyzing
Block #96,514,354
24 transactions · 23 stateful · 2026-08-16 14:32:06 UTC
Parallelism
58/100
Blocked
61%
Avg conflicts / tx
2.04
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #96,514,354 · 24 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
1w02w13w04w25w36w49w510w615w716w822w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2fc6a7aa…b4f4
0x34b655…2a6f
16 touches
28 conflicts
0x424934c8…f2f1
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0x733a5000…6e67
0x34b655…2a6f
6 touches
3 conflicts
0xf219f7cf…7379
0xa6afd3…d132
6 touches
3 conflicts
0x00000000…00c9
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
28 conflicts on slot 0x2fc6a7aae7…18b4f4
Audit this contract →
← previous block·next block →recent activity