← previous blocknext block →recent activity
Analyzing
Block #96,708,827
32 transactions · 31 stateful · 2026-08-17 06:50:12 UTC
Parallelism
63/100
Blocked
68%
Avg conflicts / tx
2.31
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #96,708,827 · 32 txs across 12 waves · depth 12
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w08w09w110w111w212w313w314w415w516w617w718w720w322w123w824w225w226w327w930w1031w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x734ee320…caae
0x34b655…2a6f
16 touches
28 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
12 touches
15 conflicts
0x52b477bc…7ccf
0x34b655…2a6f
12 touches
15 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xd676e291…3ecf
0x34b655…2a6f
8 touches
6 conflicts
0x6d43ee99…bdd4
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
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 0x734ee32053…cecaae
Audit this contract →
← previous block·next block →recent activity