← previous blocknext block →recent activity
Analyzing
Block #96,591,822
17 transactions · 13 stateful · 2026-08-16 21:01:44 UTC
Parallelism
65/100
Blocked
38%
Avg conflicts / tx
0.41
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #96,591,822 · 17 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w36w415w016w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9a3463f0…0b73
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x0d488000…3831
0x34b655…2a6f
4 touches
1 conflict
0x745952b2…d90c
0x34b655…2a6f
4 touches
1 conflict
0x8d4c0bb9…ccd3
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…001e
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…002e
0x1b6862…e19c
2 touches
0 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
3 conflicts on slot 0x9a3463f0c8…ca0b73
Audit this contract →
← previous block·next block →recent activity