← previous blocknext block →recent activity
Analyzing
Block #97,690,343
19 transactions · 17 stateful · 2026-08-20 18:03:50 UTC
Parallelism
68/100
Blocked
41%
Avg conflicts / tx
0.79
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #97,690,343 · 19 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
1w02w05w07w09w110w112w013w115w216w317w418w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x30f3ece3…c237
0x34b655…2a6f
8 touches
6 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x7aad02c6…b979
0x34b655…2a6f
6 touches
3 conflicts
0x247c79f2…e698
0x34b655…2a6f
4 touches
1 conflict
0x2c500099…5ee3
0x34b655…2a6f
4 touches
1 conflict
0x4a910bbf…9805
0x34b655…2a6f
4 touches
1 conflict
0x7ee110ef…8394
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 0x30f3ece315…53c237
Audit this contract →
← previous block·next block →recent activity