← previous blocknext block →recent activity
Analyzing
Block #97,726,691
16 transactions · 16 stateful · 2026-08-20 21:08:26 UTC
Parallelism
75/100
Blocked
31%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,726,691 · 16 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
1w02w06w17w28w313w014w115w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x25957369…c648
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0x10b01310…f3cb
0x34b655…2a6f
4 touches
1 conflict
0x48ddcaaa…2cd8
0x34b655…2a6f
4 touches
1 conflict
0x710a942c…4501
0x34b655…2a6f
4 touches
1 conflict
0x710a942c…4502
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
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 0x25957369b1…4cc648
Audit this contract →
← previous block·next block →recent activity