← previous blocknext block →recent activity
Analyzing
Block #97,606,056
21 transactions · 21 stateful · 2026-08-20 10:51:16 UTC
Parallelism
71/100
Blocked
38%
Avg conflicts / tx
0.71
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #97,606,056 · 21 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w16w27w38w09w311w015w419w520w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2e8d2713…7b58
0x34b655…2a6f
8 touches
6 conflicts
0xcbfeb997…6e11
0x34b655…2a6f
6 touches
3 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0xcb46fee6…837b
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0x7aad02c6…b979
0x34b655…2a6f
4 touches
1 conflict
0x7de57974…f5ba
0x34b655…2a6f
4 touches
1 conflict
0x948836ff…59ab
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
6 conflicts on slot 0x2e8d2713a5…cf7b58
Audit this contract →
← previous block·next block →recent activity