← previous blocknext block →recent activity
Analyzing
Block #96,521,456
13 transactions · 11 stateful · 2026-08-16 15:07:49 UTC
Parallelism
77/100
Blocked
36%
Avg conflicts / tx
0.46
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,521,456 · 13 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w06w17w28w09w211w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa35b93d5…34c9
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…641f
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
0x7c09c53e…64b4
0x34b655…2a6f
6 touches
3 conflicts
0x7e1d87b8…291c
0x34b655…2a6f
6 touches
3 conflicts
0x87ab06cc…147e
0x34b655…2a6f
5 touches
3 conflicts
0x177211e2…1c2d
0x754704…b603
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
3 conflicts on slot 0xa35b93d558…3034c9
Audit this contract →
← previous block·next block →recent activity