← previous blocknext block →recent activity
Analyzing
Block #97,826,818
13 transactions · 12 stateful · 2026-08-21 05:33:43 UTC
Parallelism
69/100
Blocked
50%
Avg conflicts / tx
0.46
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,826,818 · 13 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
1w02w13w04w15w06w17w28w311w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x08d66073…e706
0x34b655…2a6f
4 touches
1 conflict
0x2728cd60…78cc
0x34b655…2a6f
4 touches
1 conflict
0x2acf7e76…bbe8
0x34b655…2a6f
4 touches
1 conflict
0x2f08b71f…0bea
0x34b655…2a6f
4 touches
1 conflict
0x438f4336…47c9
0x34b655…2a6f
4 touches
1 conflict
0x5eb187dd…b1d6
0x34b655…2a6f
4 touches
1 conflict
0x68c07cb9…ae14
0x34b655…2a6f
4 touches
1 conflict
0x6e7e3cc9…bcc0
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 0x08d6607389…0fe706
Audit this contract →
← previous block·next block →recent activity