← previous blocknext block →recent activity
Analyzing
Block #97,842,563
21 transactions · 19 stateful · 2026-08-21 06:53:26 UTC
Parallelism
81/100
Blocked
37%
Avg conflicts / tx
0.76
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,842,563 · 21 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
2w03w05w16w07w18w212w213w316w319w020w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7753b200…57a7
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0xec1d6663…6042
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x5b1d9d9c…259d
0x34b655…2a6f
4 touches
1 conflict
0x660912f0…d43a
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 0x7753b2001e…c057a7
Audit this contract →
← previous block·next block →recent activity