← previous blocknext block →recent activity
Analyzing
Block #97,466,695
21 transactions · 21 stateful · 2026-08-19 23:07:22 UTC
Parallelism
71/100
Blocked
52%
Avg conflicts / tx
1.1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #97,466,695 · 21 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
2w04w15w26w07w08w19w210w211w312w413w115w117w520w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x806c6904…3d63
0x34b655…2a6f
8 touches
6 conflicts
0x75fe24d2…46f9
0x34b655…2a6f
6 touches
3 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
6 touches
3 conflicts
0xbde524f4…43bf
0x34b655…2a6f
6 touches
3 conflicts
0xec7d120d…7084
0x34b655…2a6f
6 touches
3 conflicts
0x2dcc0868…26bf
0x34b655…2a6f
6 touches
3 conflicts
0x5cfec795…7c0e
0x34b655…2a6f
4 touches
1 conflict
0x98998c62…22b5
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 0x806c6904e3…af3d63
Audit this contract →
← previous block·next block →recent activity