← previous blocknext block →recent activity
Analyzing
Block #97,397,913
17 transactions · 16 stateful · 2026-08-19 17:19:35 UTC
Parallelism
88/100
Blocked
19%
Avg conflicts / tx
0.29
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #97,397,913 · 17 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w09w010w112w116w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc9e81364…2ceb
0x34b655…2a6f
4 touches
1 conflict
0xaeb130b3…92e2
0x34b655…2a6f
4 touches
1 conflict
0xb74116b4…dc4a
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x52f856f5…bee6
0x34b655…2a6f
2 touches
0 conflicts
0x5310d373…118f
0x34b655…2a6f
2 touches
0 conflicts
0x705ab4ae…0162
0x34b655…2a6f
2 touches
0 conflicts
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
1 conflict on slot 0xc9e81364e4…d82ceb
Audit this contract →
← previous block·next block →recent activity