← previous blocknext block →recent activity
Analyzing
Block #97,519,283
29 transactions · 24 stateful · 2026-08-20 03:32:11 UTC
Parallelism
83/100
Blocked
33%
Avg conflicts / tx
0.45
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #97,519,283 · 29 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w08w09w010w011w112w113w217w020w321w222w423w428w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc158f1d9…bc17
0x34b655…2a6f
6 touches
3 conflicts
0xd4c892f6…f15d
0x065c9d…c394
6 touches
3 conflicts
0x002fed35…79fa
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…0019
0x1b6862…e19c
4 touches
1 conflict
0xcb45d9d6…cb81
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x60949736…876e
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 0xc158f1d988…ebbc17
Audit this contract →
← previous block·next block →recent activity