← previous blocknext block →recent activity
Analyzing
Block #97,726,441
19 transactions · 18 stateful · 2026-08-20 21:07:10 UTC
Parallelism
84/100
Blocked
39%
Avg conflicts / tx
0.58
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #97,726,441 · 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
1w02w03w05w06w17w29w110w211w116w017w218w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x280d1119…ee4d
0x34b655…2a6f
6 touches
3 conflicts
0x0adfec5f…8741
0xa6afd3…d132
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xbde524f4…43bf
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x9a7ae597…3816
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
3 conflicts on slot 0x280d1119b5…8aee4d
Audit this contract →
← previous block·next block →recent activity