← previous blocknext block →recent activity
Analyzing
Block #97,739,315
18 transactions · 17 stateful · 2026-08-20 22:11:58 UTC
Parallelism
67/100
Blocked
53%
Avg conflicts / tx
0.72
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #97,739,315 · 18 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
1w02w13w26w07w18w29w310w411w412w515w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x103de0…bb55
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x84585d11…6ae7
0x34b655…2a6f
6 touches
3 conflicts
0x91132a87…2232
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0x676f9f01…a8ac
0x34b655…2a6f
4 touches
1 conflict
0x6c60fbcf…8744
0x34b655…2a6f
4 touches
1 conflict
0x7aad02c6…b979
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: 0x103de0b5…25bb55
3 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity