← previous blocknext block →recent activity
Analyzing
Block #97,397,329
25 transactions · 22 stateful · 2026-08-19 17:16:38 UTC
Parallelism
84/100
Blocked
36%
Avg conflicts / tx
0.56
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,397,329 · 25 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
1w02w03w14w05w16w17w08w19w212w013w317w124w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd042b223…f61c
0x34b655…2a6f
6 touches
3 conflicts
0x6f6aa736…a698
0x34b655…2a6f
6 touches
3 conflicts
0x729c91b8…9539
0x188d58…ea8e
4 touches
1 conflict
0x56a919c4…ab49
0xee8c0e…1242
4 touches
1 conflict
0x729c91b8…9537
0x188d58…ea8e
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xec431e8f…8c4d
0x34b655…2a6f
4 touches
1 conflict
0xec7d120d…7084
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 0xd042b223d5…31f61c
Audit this contract →
← previous block·next block →recent activity