← previous blocknext block →recent activity
Analyzing
Block #97,826,789
18 transactions · 17 stateful · 2026-08-21 05:33:35 UTC
Parallelism
78/100
Blocked
35%
Avg conflicts / tx
0.56
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,826,789 · 18 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
1w04w05w17w08w19w010w113w214w317w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x737acb78…fce8
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0xaae6463e…bfcc
0x34b655…2a6f
6 touches
3 conflicts
0x7620a832…4ab4
0x34b655…2a6f
6 touches
3 conflicts
0x757b0543…e087
0x34b655…2a6f
6 touches
3 conflicts
0xe9be57eb…9610
0x34b655…2a6f
4 touches
1 conflict
0x2728cd60…78cc
0x34b655…2a6f
4 touches
1 conflict
0x90d32d93…7c17
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
6 conflicts on slot 0x737acb7813…fafce8
Audit this contract →
← previous block·next block →recent activity