← previous blocknext block →recent activity
Analyzing
Block #96,560,988
10 transactions · 9 stateful · 2026-08-16 18:26:38 UTC
Parallelism
70/100
Blocked
67%
Avg conflicts / tx
0.8
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,560,988 · 10 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
1w02w03w14w25w16w27w28w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6246af59…213f
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xfc8cd993…5c11
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x7c09c53e…64b4
0x34b655…2a6f
4 touches
1 conflict
0xafb8e71e…9285
0x34b655…2a6f
4 touches
1 conflict
0x4c702894…9f4c
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
3 conflicts on slot 0x6246af5912…9c213f
Audit this contract →
← previous block·next block →recent activity