← previous blocknext block →recent activity
Analyzing
Block #96,599,690
14 transactions · 13 stateful · 2026-08-16 21:41:18 UTC
Parallelism
64/100
Blocked
38%
Avg conflicts / tx
0.93
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #96,599,690 · 14 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
1w02w05w16w28w010w311w412w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xeafde96f…bf5e
0x34b655…2a6f
10 touches
10 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xb46bb9bf…deb7
0x34b655…2a6f
6 touches
3 conflicts
0xc105dd15…cbbc
0x34b655…2a6f
6 touches
3 conflicts
0x21280422…0930
0x34b655…2a6f
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
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
10 conflicts on slot 0xeafde96fa9…9cbf5e
Audit this contract →
← previous block·next block →recent activity