← previous blocknext block →recent activity
Analyzing
Block #97,690,319
23 transactions · 20 stateful · 2026-08-20 18:03:43 UTC
Parallelism
65/100
Blocked
50%
Avg conflicts / tx
1.26
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #97,690,319 · 23 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w17w08w110w112w213w218w319w420w521w622w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xb409e204…89ac
0x34b655…2a6f
8 touches
6 conflicts
0x18b11fba…c92a
0x34b655…2a6f
6 touches
3 conflicts
0x422f657b…279e
0x34b655…2a6f
6 touches
3 conflicts
0xb42ffae8…7bb9
0x34b655…2a6f
5 touches
3 conflicts
0x393ade60…3be9
0xa6afd3…d132
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
21 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity