← previous blocknext block →recent activity

Analyzing

Block #97,657,446

17 transactions · 17 stateful · 2026-08-20 15:14:57 UTC

Parallelism

59/100

Blocked

53%

Avg conflicts / tx

1.18

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #97,657,446  ·  17 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

0xb3fb9fb5…64db

0x34b655…2a6f

8 touches
6 conflicts

0x14062aed…6e43

0x34b655…2a6f

6 touches
3 conflicts

0xec7d120d…7084

0x34b655…2a6f

6 touches
3 conflicts

0x66432bdc…57dc

0x34b655…2a6f

6 touches
3 conflicts

0x94610395…f8ee

0xa6afd3…d132

4 touches
1 conflict

0x7265675e…d0d3

0x34b655…2a6f

4 touches
1 conflict

0x8a0d91a0…2b15

0x34b655…2a6f

4 touches
1 conflict

0xa227f33f…c929

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 0xb3fb9fb561…7664db

← previous block·next block →recent activity