← previous blocknext block →recent activity
Analyzing
Block #97,397,297
17 transactions · 16 stateful · 2026-08-19 17:16:28 UTC
Parallelism
82/100
Blocked
25%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #97,397,297 · 17 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
2w05w06w18w09w111w212w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6f6aa736…a698
0x34b655…2a6f
6 touches
3 conflicts
0x7de57974…f5ba
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
0x4179f9bf…d737
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x22538b4b…9b89
0x34b655…2a6f
4 touches
1 conflict
0x4d55d0be…e30c
0x34b655…2a6f
3 touches
1 conflict
0x4bfdcd51…9b58
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 0x6f6aa736ef…34a698
Audit this contract →
← previous block·next block →recent activity