← previous blocknext block →recent activity
Analyzing
Block #97,517,949
22 transactions · 19 stateful · 2026-08-20 03:25:28 UTC
Parallelism
86/100
Blocked
37%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #97,517,949 · 22 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
3w07w08w19w211w012w113w215w016w119w221w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb3fb9fb5…64db
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x9d67cfe8…0db6
0xa6afd3…d132
4 touches
1 conflict
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0x00e21a9f…3583
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35d
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0x5caf9f43…a348
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 0xb3fb9fb561…7664db
Audit this contract →
← previous block·next block →recent activity