← previous blocknext block →recent activity
Analyzing
Block #97,513,671
20 transactions · 19 stateful · 2026-08-20 03:03:56 UTC
Parallelism
85/100
Blocked
32%
Avg conflicts / tx
0.45
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #97,513,671 · 20 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
2w06w07w18w110w011w113w217w018w119w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2d40fa6f…2e02
0x34b655…2a6f
6 touches
3 conflicts
0x61f7bce8…3e84
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x8f63f383…6eda
0x34b655…2a6f
4 touches
1 conflict
0xbc4ae46f…2a25
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
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
3 conflicts on slot 0x2d40fa6fb7…2f2e02
Audit this contract →
← previous block·next block →recent activity