← previous blocknext block →recent activity
Analyzing
Block #97,614,275
30 transactions · 27 stateful · 2026-08-20 11:33:03 UTC
Parallelism
73/100
Blocked
52%
Avg conflicts / tx
1.17
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #97,614,275 · 30 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
1w02w17w08w110w211w012w113w214w015w316w417w518w519w620w723w125w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x737acb78…fce8
0x34b655…2a6f
10 touches
10 conflicts
0xac2a0273…721b
0x34b655…2a6f
10 touches
10 conflicts
0xec7d120d…7084
0x34b655…2a6f
10 touches
10 conflicts
0x69352f9f…5449
0x34b655…2a6f
8 touches
6 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
8 touches
6 conflicts
0x318ac0bb…6b9c
0x34b655…2a6f
6 touches
3 conflicts
0xb73859b9…2882
0x40c49f…2af0
4 touches
1 conflict
0xe722a908…2b55
0x40c49f…2af0
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
10 conflicts on slot 0x737acb7813…fafce8
Audit this contract →
← previous block·next block →recent activity