← previous blocknext block →recent activity
Analyzing
Block #96,294,763
13 transactions · 13 stateful · 2026-08-15 20:07:22 UTC
Parallelism
54/100
Blocked
46%
Avg conflicts / tx
1.31
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #96,294,763 · 13 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w37w38w411w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4c4b7a66…c877
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xa5a8ffca…8de2
0x34b655…2a6f
6 touches
3 conflicts
0xe561281f…7569
0x34b655…2a6f
4 touches
1 conflict
0x2029b74e…c206
0x34b655…2a6f
4 touches
1 conflict
0x28be48f5…d50b
0x34b655…2a6f
4 touches
1 conflict
0x48b13e5e…3c2a
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 0x4c4b7a66e4…20c877
Audit this contract →
← previous block·next block →recent activity