← previous blocknext block →recent activity
Analyzing
Block #97,479,001
14 transactions · 13 stateful · 2026-08-20 00:09:31 UTC
Parallelism
79/100
Blocked
38%
Avg conflicts / tx
0.43
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #97,479,001 · 14 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
1w02w13w05w17w29w210w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x516e9b35…57e7
0x34b655…2a6f
6 touches
3 conflicts
0xca2027b9…193c
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x655aa1bb…138c
0x40c49f…2af0
4 touches
1 conflict
0xc3d48eae…1afb
0x40c49f…2af0
4 touches
1 conflict
0xdfffe05f…e6d3
0x40c49f…2af0
4 touches
1 conflict
0xf30ae07c…79b9
0x40c49f…2af0
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
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 0x516e9b35e5…8857e7
Audit this contract →
← previous block·next block →recent activity