← previous blocknext block →recent activity
Analyzing
Block #97,397,391
18 transactions · 18 stateful · 2026-08-19 17:16:57 UTC
Parallelism
72/100
Blocked
28%
Avg conflicts / tx
0.56
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #97,397,391 · 18 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w05w16w07w28w311w113w014w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaab9957c…a4bf
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x984e4d8c…9912
0x34b655…2a6f
4 touches
1 conflict
0xb24a9fb5…f3d7
0xa6afd3…d132
4 touches
1 conflict
0x261cbea7…e35d
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35e
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 0xaab9957cf9…8aa4bf
Audit this contract →
← previous block·next block →recent activity