← previous blocknext block →recent activity
Analyzing
Block #97,515,142
33 transactions · 30 stateful · 2026-08-20 03:11:20 UTC
Parallelism
88/100
Blocked
40%
Avg conflicts / tx
0.73
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,515,142 · 33 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
3w05w07w08w09w110w111w212w317w018w019w123w125w226w328w229w231w332w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6b3b4671…580f
0x34b655…2a6f
8 touches
6 conflicts
0xe606662e…0efc
0x34b655…2a6f
6 touches
3 conflicts
0xec7d120d…7084
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x9c381bc1…5f5e
0xa6afd3…d132
6 touches
3 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
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 0x6b3b4671f1…23580f
Audit this contract →
← previous block·next block →recent activity