← previous blocknext block →recent activity
Analyzing
Block #97,517,097
24 transactions · 21 stateful · 2026-08-20 03:21:10 UTC
Parallelism
75/100
Blocked
43%
Avg conflicts / tx
0.79
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #97,517,097 · 24 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w06w07w08w110w111w212w315w316w418w019w122w523w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x21d6593f…26e1
0x34b655…2a6f
6 touches
3 conflicts
0xca401ec1…58f8
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x38c47502…1005
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x1df6297e…84cc
0x34b655…2a6f
4 touches
1 conflict
0x3d354ff0…b7c5
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 0x21d6593f38…9526e1
Audit this contract →
← previous block·next block →recent activity