← previous blocknext block →recent activity
Analyzing
Block #97,513,097
38 transactions · 32 stateful · 2026-08-20 03:01:03 UTC
Parallelism
63/100
Blocked
66%
Avg conflicts / tx
1.95
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #97,513,097 · 38 txs across 14 waves · depth 14
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w07w38w49w510w511w612w713w815w916w1017w918w1119w1221w1025w1032w1235w1337w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1ba73d09…ba89
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xc38a1e34…37c3
0x34b655…2a6f
10 touches
10 conflicts
0xb97c885b…2933
0x34b655…2a6f
10 touches
10 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
10 touches
10 conflicts
0xec7d120d…7084
0x34b655…2a6f
8 touches
6 conflicts
0x287f71b4…5a6a
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
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 0x1ba73d0943…35ba89
Audit this contract →
← previous block·next block →recent activity