← previous blocknext block →recent activity
Analyzing
Block #96,837,172
18 transactions · 17 stateful · 2026-08-17 17:35:45 UTC
Parallelism
56/100
Blocked
47%
Avg conflicts / tx
1.5
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #96,837,172 · 18 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
1w02w13w24w310w011w112w413w514w617w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf36587f6…b0a2
0x34b655…2a6f
14 touches
21 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xac3e4969…39e9
0x34b655…2a6f
8 touches
6 conflicts
0x5d1ac445…5233
0x34b655…2a6f
4 touches
1 conflict
0x62a8dd5f…3664
0x34b655…2a6f
4 touches
1 conflict
0xa9af9157…5a6e
0x34b655…2a6f
4 touches
1 conflict
0xabf57eb6…416d
0x34b655…2a6f
4 touches
1 conflict
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 0xf36587f6dc…62b0a2
Audit this contract →
← previous block·next block →recent activity