← previous blocknext block →recent activity
Analyzing
Block #96,795,563
17 transactions · 16 stateful · 2026-08-17 14:06:28 UTC
Parallelism
53/100
Blocked
63%
Avg conflicts / tx
1.12
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #96,795,563 · 17 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w15w26w27w38w49w513w615w716w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb3fb9fb5…64db
0x34b655…2a6f
10 touches
10 conflicts
0xec7d120d…7084
0x34b655…2a6f
6 touches
3 conflicts
0x4cabb80a…46bf
0x34b655…2a6f
4 touches
1 conflict
0x53f393fa…00b9
0x34b655…2a6f
4 touches
1 conflict
0x03aa8b26…118a
0x34b655…2a6f
4 touches
1 conflict
0xacd1b162…bee6
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x966e45cf…0f25
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
10 conflicts on slot 0xb3fb9fb561…7664db
Audit this contract →
← previous block·next block →recent activity