← previous blocknext block →recent activity
Analyzing
Block #97,736,303
43 transactions · 26 stateful · 2026-08-20 21:56:49 UTC
Parallelism
93/100
Blocked
35%
Avg conflicts / tx
0.23
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #97,736,303 · 43 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w05w18w09w010w014w015w119w020w126w030w131w132w133w235w142w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0x103de0…bb55
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x0bc43347…93d4
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xcce2fd99…a8eb
0x3bd359…433a
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity