← previous blocknext block →recent activity
Analyzing
Block #96,325,307
11 transactions · 9 stateful · 2026-08-15 22:40:59 UTC
Parallelism
55/100
Blocked
56%
Avg conflicts / tx
0.64
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #96,325,307 · 11 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
1w03w16w27w38w410w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x427dec7f…61c6
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x5df7cf2b…bbe5
0x34b655…2a6f
4 touches
1 conflict
0x5e6a725f…3b35
0x34b655…2a6f
4 touches
1 conflict
0x7ef4ba09…2a25
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xda114b80…e2e6
0x34b655…2a6f
4 touches
1 conflict
0x06726618…fafd
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 0x427dec7fbc…3e61c6
Audit this contract →
← previous block·next block →recent activity