← previous blocknext block →recent activity
Analyzing
Block #97,728,299
25 transactions · 23 stateful · 2026-08-20 21:16:32 UTC
Parallelism
80/100
Blocked
39%
Avg conflicts / tx
0.68
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #97,728,299 · 25 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w06w18w09w110w211w314w215w017w121w022w123w424w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc56bb09e…9c88
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x886db264…846e
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x303f4ecc…ab9b
0x34b655…2a6f
5 touches
3 conflicts
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
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
10 conflicts on slot 0xc56bb09e4e…b79c88
Audit this contract →
← previous block·next block →recent activity