← previous blocknext block →recent activity
Analyzing
Block #96,350,966
26 transactions · 25 stateful · 2026-08-16 00:50:02 UTC
Parallelism
92/100
Blocked
8%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,350,966 · 26 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
2w03w022w124w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x16f2b4e1…e98b
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0xc782ec05…5bb2
0xa6afd3…d132
4 touches
1 conflict
0x0eac6378…36f4
0x34b655…2a6f
2 touches
0 conflicts
0x15be757a…275e
0x34b655…2a6f
2 touches
0 conflicts
0x15be757a…275f
0x34b655…2a6f
2 touches
0 conflicts
0x1a3d2527…8ca0
0x34b655…2a6f
2 touches
0 conflicts
0x31b39922…1e65
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 0x16f2b4e165…c7e98b
Audit this contract →
← previous block·next block →recent activity