← previous blocknext block →recent activity
Analyzing
Block #96,608,673
10 transactions · 9 stateful · 2026-08-16 22:26:30 UTC
Parallelism
80/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,608,673 · 10 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w18w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x74e0d9d2…47d7
0x34b655…2a6f
4 touches
1 conflict
0x7fb99184…e8bb
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x054afe69…16e8
0x34b655…2a6f
2 touches
0 conflicts
0x0f6aef87…8137
0x34b655…2a6f
2 touches
0 conflicts
0x152f8e3d…3da0
0x34b655…2a6f
2 touches
0 conflicts
0x23ce455e…41ae
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 0x74e0d9d2dd…b147d7
Audit this contract →
← previous block·next block →recent activity