← previous blocknext block →recent activity
Analyzing
Block #97,503,360
20 transactions · 17 stateful · 2026-08-20 02:12:03 UTC
Parallelism
75/100
Blocked
41%
Avg conflicts / tx
0.8
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #97,503,360 · 20 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
2w05w06w17w28w39w212w313w419w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xbde524f4…43bf
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xe1580ebb…bbe7
0x34b655…2a6f
6 touches
3 conflicts
0x52454034…576f
0x34b655…2a6f
6 touches
3 conflicts
0xc1da8f73…484c
0x34b655…2a6f
6 touches
3 conflicts
0x469dac8d…3411
0x34b655…2a6f
4 touches
1 conflict
0x1014d868…5601
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 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity