← previous blocknext block →recent activity
Analyzing
Block #97,514,245
16 transactions · 15 stateful · 2026-08-20 03:06:50 UTC
Parallelism
63/100
Blocked
53%
Avg conflicts / tx
1.31
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #97,514,245 · 16 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
1w02w03w15w06w17w28w39w410w011w214w115w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1ba73d09…ba89
0x34b655…2a6f
12 touches
15 conflicts
0x22414fbb…1edf
0xa6afd3…d132
6 touches
3 conflicts
0x4e58f1d6…2fca
0x34b655…2a6f
4 touches
1 conflict
0xa54890e1…facd
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xec7d120d…7084
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
15 conflicts on slot 0x1ba73d0943…35ba89
Audit this contract →
← previous block·next block →recent activity