← previous blocknext block →recent activity
Analyzing
Block #96,299,270
18 transactions · 18 stateful · 2026-08-15 20:30:02 UTC
Parallelism
72/100
Blocked
61%
Avg conflicts / tx
1.17
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #96,299,270 · 18 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
1w02w13w24w35w16w07w19w010w111w213w314w416w317w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x9f60dbd0…5f36
0x34b655…2a6f
8 touches
6 conflicts
0x06372454…76a3
0xd32edf…ff58
7 touches
6 conflicts
0x2d7ea048…d78e
0x34b655…2a6f
4 touches
1 conflict
0x3c7c65d0…0b52
0x34b655…2a6f
4 touches
1 conflict
0x19840da5…08b8
0x34b655…2a6f
4 touches
1 conflict
0x510d2be6…2a87
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity