← previous blocknext block →recent activity
Analyzing
Block #96,387,923
10 transactions · 10 stateful · 2026-08-16 03:55:55 UTC
Parallelism
60/100
Blocked
30%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #96,387,923 · 10 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
1w06w17w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x84ee6168…3f13
0x34b655…2a6f
6 touches
3 conflicts
0x2b64d0d7…af06
0x34b655…2a6f
6 touches
3 conflicts
0x56a284d9…32e4
0x34b655…2a6f
6 touches
3 conflicts
0x7d215b9c…8192
0x34b655…2a6f
6 touches
3 conflicts
0xbf36c8df…3bc1
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…641f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…00c9
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
3 conflicts on slot 0x84ee616829…843f13
Audit this contract →
← previous block·next block →recent activity