← previous blocknext block →recent activity
Analyzing
Block #97,606,117
18 transactions · 17 stateful · 2026-08-20 10:51:35 UTC
Parallelism
72/100
Blocked
29%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #97,606,117 · 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
1w05w06w07w18w211w015w316w417w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x214dc988…ba27
0x34b655…2a6f
6 touches
3 conflicts
0x2e5cdd04…22ab
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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
0xe6bc2705…d15b
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
3 conflicts on slot 0x214dc98868…30ba27
Audit this contract →
← previous block·next block →recent activity