← previous blocknext block →recent activity
Analyzing
Block #97,396,140
15 transactions · 13 stateful · 2026-08-19 17:10:36 UTC
Parallelism
80/100
Blocked
31%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #97,396,140 · 15 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
1w02w05w17w08w29w114w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbfe333a4…687f
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0x5b63b363…ffda
0x34b655…2a6f
4 touches
1 conflict
0x5e3d39c2…f600
0x34b655…2a6f
4 touches
1 conflict
0xb4527790…c282
0x34b655…2a6f
4 touches
1 conflict
0xd2bfc069…f059
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x00000000…001e
0x1b6862…e19c
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
3 conflicts on slot 0xbfe333a41e…31687f
Audit this contract →
← previous block·next block →recent activity