← previous blocknext block →recent activity
Analyzing
Block #97,501,276
33 transactions · 21 stateful · 2026-08-20 02:01:34 UTC
Parallelism
88/100
Blocked
43%
Avg conflicts / tx
0.42
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,501,276 · 33 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
1w06w08w113w015w016w117w218w321w022w123w225w026w131w332w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x246e5638…b635
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x28b98e1a…3f06
0x065c9d…c394
4 touches
1 conflict
0xa4f80979…4d71
0x065c9d…c394
4 touches
1 conflict
0x11258774…9892
0x2a68ba…90c5
4 touches
1 conflict
0x0214b385…f83d
0x34b655…2a6f
4 touches
1 conflict
0x1fc4aac9…2dd0
0x34b655…2a6f
4 touches
1 conflict
0x29a945df…bcd8
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 0x246e5638a2…07b635
Audit this contract →
← previous block·next block →recent activity