← previous blocknext block →recent activity
Analyzing
Block #97,395,827
33 transactions · 30 stateful · 2026-08-19 17:09:01 UTC
Parallelism
85/100
Blocked
47%
Avg conflicts / tx
1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #97,395,827 · 33 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
1w08w09w010w111w112w213w214w315w316w417w418w319w132w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xec7d120d…7084
0x34b655…2a6f
10 touches
10 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
10 touches
10 conflicts
0xc9b377bf…8bc5
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0x40c49f…2af0
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x54f7f60f…43cc
0x34b655…2a6f
4 touches
1 conflict
0x6bc293e9…556e
0x34b655…2a6f
4 touches
1 conflict
0x6f6aa736…a698
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
10 conflicts on slot 0xec7d120df9…5d7084
Audit this contract →
← previous block·next block →recent activity