← previous blocknext block →recent activity
Analyzing
Block #96,663,863
13 transactions · 12 stateful · 2026-08-17 03:04:04 UTC
Parallelism
69/100
Blocked
42%
Avg conflicts / tx
0.62
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #96,663,863 · 13 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
2w04w15w26w28w211w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x17dd6839…0f1a
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xfbe6a366…8ca1
0x34b655…2a6f
4 touches
1 conflict
0x3fed1570…be73
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x8c381258…46d0
0x34b655…2a6f
4 touches
1 conflict
0x90cb88ac…2a36
0x34b655…2a6f
4 touches
1 conflict
0x91b0f8ed…6bd6
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 0x17dd68395c…f90f1a
Audit this contract →
← previous block·next block →recent activity