← previous blocknext block →recent activity
Analyzing
Block #96,603,664
19 transactions · 17 stateful · 2026-08-16 22:01:18 UTC
Parallelism
63/100
Blocked
59%
Avg conflicts / tx
1.84
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #96,603,664 · 19 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w15w16w27w38w412w213w414w515w618w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0x840d3ab7…c8c4
0x34b655…2a6f
8 touches
6 conflicts
0xc0e948e9…b235
0x34b655…2a6f
7 touches
6 conflicts
0x5fde4971…aac9
0x34b655…2a6f
6 touches
3 conflicts
0xaedae560…7f27
0x34b655…2a6f
6 touches
3 conflicts
0xa9988419…9f45
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
15 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity