← previous blocknext block →recent activity
Analyzing
Block #96,619,889
16 transactions · 15 stateful · 2026-08-16 23:22:54 UTC
Parallelism
69/100
Blocked
40%
Avg conflicts / tx
0.56
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #96,619,889 · 16 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w06w19w210w311w113w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4acbdbcf…a8c6
0x34b655…2a6f
8 touches
6 conflicts
0x8b98eea2…60b0
0x34b655…2a6f
8 touches
6 conflicts
0xf6191640…5627
0x34b655…2a6f
6 touches
3 conflicts
0xa57576bb…e01f
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…002f
0x1b6862…e19c
4 touches
1 conflict
0xd5b10148…e638
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x482471ad…122f
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
6 conflicts on slot 0x4acbdbcf7f…d0a8c6
Audit this contract →
← previous block·next block →recent activity