← previous blocknext block →recent activity
Analyzing
Block #97,718,670
28 transactions · 24 stateful · 2026-08-20 20:27:48 UTC
Parallelism
86/100
Blocked
42%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,718,670 · 28 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
1w03w04w15w06w17w29w016w017w118w119w222w324w025w126w327w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x68c23664…74c4
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xe8bf0a0a…909f
0x065c9d…c394
5 touches
3 conflicts
0x00000000…0002
0x103de0…bb55
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x2c539d94…b63a
0x34b655…2a6f
4 touches
1 conflict
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
3 conflicts on slot 0x68c2366471…c574c4
Audit this contract →
← previous block·next block →recent activity