← previous blocknext block →recent activity

Analyzing

Block #97,690,212

23 transactions · 20 stateful · 2026-08-20 18:03:10 UTC

Parallelism

70/100

Blocked

45%

Avg conflicts / tx

0.87

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #97,690,212  ·  23 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others

Conflict graph

Blocked by

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0xca841faa…486a

0x34b655…2a6f

12 touches
15 conflicts

0xe5bb3628…e5f1

0x34b655…2a6f

6 touches
3 conflicts

0x30f3ece3…c237

0x34b655…2a6f

6 touches
3 conflicts

0x62611f9e…92c3

0x34b655…2a6f

4 touches
1 conflict

0x68297b76…8e24

0x34b655…2a6f

4 touches
1 conflict

0x74fd0a9b…3aaa

0x34b655…2a6f

4 touches
1 conflict

0x764c3e36…c6db

0x34b655…2a6f

4 touches
1 conflict

0x828a2c9d…a150

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

15 conflicts on slot 0xca841faae5…71486a

← previous block·next block →recent activity