← previous blocknext block →recent activity
Analyzing
Block #97,568,418
23 transactions · 22 stateful · 2026-08-20 07:40:58 UTC
Parallelism
83/100
Blocked
41%
Avg conflicts / tx
0.48
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,568,418 · 23 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w04w15w26w27w210w012w013w114w117w121w322w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc38a1e34…37c3
0x34b655…2a6f
6 touches
3 conflicts
0xbde524f4…43bf
0x34b655…2a6f
6 touches
3 conflicts
0x0778475b…bd75
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0xf40dd007…8944
0x065c9d…c394
4 touches
1 conflict
0x2bb0d58d…9dcf
0x34b655…2a6f
4 touches
1 conflict
0xb97c885b…2933
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
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 0xc38a1e3492…2d37c3
Audit this contract →
← previous block·next block →recent activity