← previous blocknext block →recent activity
Analyzing
Block #97,729,313
15 transactions · 14 stateful · 2026-08-20 21:21:40 UTC
Parallelism
87/100
Blocked
21%
Avg conflicts / tx
0.33
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #97,729,313 · 15 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w06w07w111w012w114w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0bc43347…93d4
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x909be59f…0d63
0x34b655…2a6f
4 touches
1 conflict
0xb7bda60c…8a2c
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe732567d…b65d
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0x00000000…002d
0x1b6862…e19c
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
1 conflict on slot 0x0bc433477d…9e93d4
Audit this contract →
← previous block·next block →recent activity