← previous blocknext block →recent activity
Analyzing
Block #97,503,315
24 transactions · 24 stateful · 2026-08-20 02:11:50 UTC
Parallelism
79/100
Blocked
42%
Avg conflicts / tx
0.63
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #97,503,315 · 24 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
1w04w05w17w08w09w110w011w114w215w117w219w020w121w322w423w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd6f857b1…bae3
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x516e9b35…57e7
0x34b655…2a6f
4 touches
1 conflict
0x69ee34d1…30f8
0x34b655…2a6f
4 touches
1 conflict
0x948836ff…59ab
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…7212
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
6 conflicts on slot 0xd6f857b1e7…f4bae3
Audit this contract →
← previous block·next block →recent activity