← previous blocknext block →recent activity
Analyzing
Block #96,700,678
11 transactions · 7 stateful · 2026-08-17 06:09:13 UTC
Parallelism
73/100
Blocked
43%
Avg conflicts / tx
0.27
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,700,678 · 11 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
5w06w18w29w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0b05d77e…6f90
0x34b655…2a6f
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x6bdb9869…7558
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x11fa73a9…776b
0x34b655…2a6f
2 touches
0 conflicts
0x15ec609d…d4a6
0x34b655…2a6f
2 touches
0 conflicts
0x1f467ce2…374a
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 0x0b05d77e66…576f90
Audit this contract →
← previous block·next block →recent activity