← previous blocknext block →recent activity
Analyzing
Block #97,530,816
23 transactions · 18 stateful · 2026-08-20 04:30:11 UTC
Parallelism
87/100
Blocked
39%
Avg conflicts / tx
0.39
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #97,530,816 · 23 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
2w03w14w06w27w08w112w016w117w221w222w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xede5b562…77c1
0x34b655…2a6f
6 touches
3 conflicts
0x11258774…9892
0x2a68ba…90c5
6 touches
3 conflicts
0xee92033a…0a66
0x065c9d…c394
5 touches
3 conflicts
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd0f6f4f2…dffa
0x34b655…2a6f
4 touches
1 conflict
0xe098738f…9bbe
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 0xede5b5625b…5977c1
Audit this contract →
← previous block·next block →recent activity