← previous blocknext block →recent activity
Analyzing
Block #96,364,396
14 transactions · 14 stateful · 2026-08-16 01:57:35 UTC
Parallelism
64/100
Blocked
50%
Avg conflicts / tx
1.14
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #96,364,396 · 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
3w04w16w08w19w210w111w212w313w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa6848351…2238
0x34b655…2a6f
8 touches
6 conflicts
0xd0919e62…a2a8
0x34b655…2a6f
8 touches
6 conflicts
0xf40e9839…0001
0x34b655…2a6f
6 touches
3 conflicts
0x3727225e…a3cf
0x34b655…2a6f
6 touches
3 conflicts
0xc01decc3…08a1
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xf1faa605…f919
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
6 conflicts on slot 0xa68483512f…c32238
Audit this contract →
← previous block·next block →recent activity