← previous blocknext block →recent activity

Analyzing

Block #97,818,550

19 transactions · 19 stateful · 2026-08-21 04:51:57 UTC

Parallelism

63/100

Blocked

47%

Avg conflicts / tx

1.16

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #97,818,550  ·  19 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

0x482471ad…122f

0x34b655…2a6f

10 touches
10 conflicts

0xc824469a…6425

0x34b655…2a6f

10 touches
10 conflicts

0x7316dc00…c16a

0x34b655…2a6f

6 touches
3 conflicts

0x525941ab…1a33

0x34b655…2a6f

6 touches
3 conflicts

0x9c2fc330…0091

0x34b655…2a6f

6 touches
3 conflicts

0x889d5e90…929a

0x2a68ba…90c5

6 touches
3 conflicts

0x6a8a1184…1970

0x34b655…2a6f

6 touches
3 conflicts

0x129d3748…3692

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

10 conflicts on slot 0x482471adbb…39122f

← previous block·next block →recent activity