← previous blocknext block →recent activity
Analyzing
Block #97,383,727
28 transactions · 24 stateful · 2026-08-19 15:49:02 UTC
Parallelism
86/100
Blocked
33%
Avg conflicts / tx
0.36
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,383,727 · 28 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w08w011w113w214w215w316w118w019w121w123w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8e7cafc0…4c76
0x34b655…2a6f
6 touches
3 conflicts
0xd9900c32…633e
0x40c49f…2af0
4 touches
1 conflict
0xef89bfa5…c133
0x34b655…2a6f
4 touches
1 conflict
0xfb0a4eb5…8be3
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x48acfd83…7ef0
0x40c49f…2af0
4 touches
1 conflict
0xa90a4122…af9a
0x40c49f…2af0
4 touches
1 conflict
0x482471ad…122f
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 0x8e7cafc06a…344c76
Audit this contract →
← previous block·next block →recent activity