← previous blocknext block →recent activity
Analyzing
Block #97,611,994
20 transactions · 16 stateful · 2026-08-20 11:21:35 UTC
Parallelism
70/100
Blocked
44%
Avg conflicts / tx
0.6
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #97,611,994 · 20 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
1w06w07w18w19w211w012w314w118w419w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x87a380d9…2d04
0x34b655…2a6f
6 touches
3 conflicts
0xcc9d4fca…ecbf
0x34b655…2a6f
6 touches
3 conflicts
0x0859a0db…c524
0x40c49f…2af0
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe5be4bd0…e382
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xec7d120d…7084
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
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 0x87a380d9ab…192d04
Audit this contract →
← previous block·next block →recent activity