← previous blocknext block →recent activity
Analyzing
Block #97,614,852
18 transactions · 17 stateful · 2026-08-20 11:35:57 UTC
Parallelism
56/100
Blocked
41%
Avg conflicts / tx
1.33
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #97,614,852 · 18 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w15w26w38w49w514w617w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
14 touches
21 conflicts
0x27537d40…722e
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
6 touches
3 conflicts
0x4480aefa…d742
0x34b655…2a6f
6 touches
3 conflicts
0x73eff9e1…025c
0x34b655…2a6f
6 touches
3 conflicts
0xf6deafb5…5c25
0x34b655…2a6f
4 touches
1 conflict
0x318ac0bb…6b9c
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
21 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity