← previous blocknext block →recent activity
Analyzing
Block #96,591,616
18 transactions · 17 stateful · 2026-08-16 21:00:42 UTC
Parallelism
50/100
Blocked
59%
Avg conflicts / tx
1.78
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #96,591,616 · 18 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
1w02w13w24w35w48w49w511w612w615w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x745952b2…d90c
0x34b655…2a6f
14 touches
21 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x48532ab5…d4c1
0x34b655…2a6f
6 touches
3 conflicts
0x48532ab5…d4c2
0x34b655…2a6f
6 touches
3 conflicts
0x0d488000…3831
0x34b655…2a6f
6 touches
3 conflicts
0x29115f5c…db4c
0x34b655…2a6f
6 touches
3 conflicts
0x3cf50d44…961b
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 0x745952b2a0…a6d90c
Audit this contract →
← previous block·next block →recent activity