← previous blocknext block →recent activity
Analyzing
Block #97,368,933
33 transactions · 30 stateful · 2026-08-19 14:32:34 UTC
Parallelism
82/100
Blocked
53%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #97,368,933 · 33 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w17w08w19w211w112w113w215w219w320w223w225w426w331w432w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5a100ac0…96d3
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x00000000…0002
0x103de0…bb55
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0x160f117d…8e90
0x065c9d…c394
6 touches
3 conflicts
0x00000000…002e
0x1b6862…e19c
4 touches
1 conflict
0x17a7f697…dcb7
0x1b6862…e19c
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
10 conflicts on slot 0x5a100ac0d9…2396d3
Audit this contract →
← previous block·next block →recent activity