← previous blocknext block →recent activity
Analyzing
Block #97,517,518
17 transactions · 16 stateful · 2026-08-20 03:23:18 UTC
Parallelism
76/100
Blocked
31%
Avg conflicts / tx
0.53
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,517,518 · 17 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
2w04w05w06w17w28w09w111w316w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x21d6593f…26e1
0x34b655…2a6f
8 touches
6 conflicts
0x2c67324f…a492
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0x5a11b0dd…bb31
0x34b655…2a6f
4 touches
1 conflict
0xccf10f13…eb5a
0x34b655…2a6f
4 touches
1 conflict
0xcdda4f74…3700
0x34b655…2a6f
4 touches
1 conflict
0xd459bf7b…92c3
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
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 0x21d6593f38…9526e1
Audit this contract →
← previous block·next block →recent activity