← previous blocknext block →recent activity
Analyzing
Block #97,519,755
19 transactions · 17 stateful · 2026-08-20 03:34:33 UTC
Parallelism
84/100
Blocked
47%
Avg conflicts / tx
0.58
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #97,519,755 · 19 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w25w06w17w18w212w013w217w218w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x38c47502…1005
0x34b655…2a6f
6 touches
3 conflicts
0x5778d110…d2e6
0xc8689a…ee79
4 touches
1 conflict
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
0xc38a1e34…37c3
0x34b655…2a6f
4 touches
1 conflict
0xe08ebe69…e3a3
0x34b655…2a6f
4 touches
1 conflict
0xec7d120d…7084
0x34b655…2a6f
4 touches
1 conflict
0xee757899…302b
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
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
3 conflicts on slot 0x38c4750210…391005
Audit this contract →
← previous block·next block →recent activity