← previous blocknext block →recent activity
Analyzing
Block #97,499,726
27 transactions · 26 stateful · 2026-08-20 01:53:47 UTC
Parallelism
89/100
Blocked
27%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #97,499,726 · 27 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
4w05w06w19w010w111w212w216w117w020w126w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xec7d120d…7084
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x4d953953…ac1f
0xa6afd3…d132
4 touches
1 conflict
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0x728f999a…832f
0x34b655…2a6f
4 touches
1 conflict
0x76ea4d0a…b4b6
0x34b655…2a6f
4 touches
1 conflict
0x886f7fe6…8b7a
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
1 conflict on slot 0xbde524f475…b143bf
Audit this contract →
← previous block·next block →recent activity