← previous blocknext block →recent activity
Analyzing
Block #96,525,528
6 transactions · 5 stateful · 2026-08-16 15:28:18 UTC
Parallelism
33/100
Blocked
60%
Avg conflicts / tx
0.83
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #96,525,528 · 6 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xff196840…a453
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x48b13e5e…3c2a
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x66bdb4c2…7ea6
0x34b655…2a6f
4 touches
1 conflict
0x742c8909…ac72
0x34b655…2a6f
4 touches
1 conflict
0x9b68408a…e609
0x34b655…2a6f
4 touches
1 conflict
0x00000000…00c9
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
3 conflicts on slot 0xff19684070…f2a453
Audit this contract →
← previous block·next block →recent activity