← previous blocknext block →recent activity
Analyzing
Block #96,797,994
13 transactions · 11 stateful · 2026-08-17 14:18:42 UTC
Parallelism
69/100
Blocked
36%
Avg conflicts / tx
0.46
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #96,797,994 · 13 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w19w210w311w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x76ed8777…1e5f
0x34b655…2a6f
6 touches
3 conflicts
0x940db765…046e
0x34b655…2a6f
6 touches
3 conflicts
0xdf00e2d7…5ada
0x34b655…2a6f
4 touches
1 conflict
0x0101906a…601c
0x34b655…2a6f
4 touches
1 conflict
0x08251b2f…33a3
0x34b655…2a6f
4 touches
1 conflict
0x2aab0897…78f7
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x8d175439…fb79
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 0x76ed8777f7…0c1e5f
Audit this contract →
← previous block·next block →recent activity