← previous blocknext block →recent activity
Analyzing
Block #96,693,691
13 transactions · 9 stateful · 2026-08-17 05:34:05 UTC
Parallelism
77/100
Blocked
33%
Avg conflicts / tx
0.23
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,693,691 · 13 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w07w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x6bdb9869…7558
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x0830f715…25c8
0x34b655…2a6f
2 touches
0 conflicts
0x0aa42ae9…ed69
0x34b655…2a6f
2 touches
0 conflicts
0x0b7c1c6b…0529
0x34b655…2a6f
2 touches
0 conflicts
0x27d74e37…a5b9
0x34b655…2a6f
2 touches
0 conflicts
0x2c2db8e9…fdc7
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity