← previous blocknext block →recent activity
Analyzing
Block #96,827,932
19 transactions · 18 stateful · 2026-08-17 16:49:17 UTC
Parallelism
58/100
Blocked
44%
Avg conflicts / tx
1.58
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #96,827,932 · 19 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w27w08w19w310w412w517w618w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
14 touches
21 conflicts
0xa58f3b3b…97c8
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0xac3e4969…39e9
0x34b655…2a6f
10 touches
10 conflicts
0x2c2db8e9…fdc7
0x34b655…2a6f
8 touches
6 conflicts
0xd597209e…9800
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xa6464996…3af9
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 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity