← previous blocknext block →recent activity
Analyzing
Block #97,514,934
14 transactions · 14 stateful · 2026-08-20 03:10:18 UTC
Parallelism
71/100
Blocked
29%
Avg conflicts / tx
0.71
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,514,934 · 14 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
4w05w06w17w18w212w013w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x95f0b212…5f7a
0x34b655…2a6f
6 touches
3 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xec7d120d…7084
0x34b655…2a6f
4 touches
1 conflict
0xedb36e17…7e26
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x60949736…876e
0x34b655…2a6f
4 touches
1 conflict
0x4353473d…dcc2
0x34b655…2a6f
2 touches
0 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
3 conflicts on slot 0x95f0b21248…e95f7a
Audit this contract →
← previous block·next block →recent activity