← previous blocknext block →recent activity

Analyzing

Block #97,843,808

24 transactions · 24 stateful · 2026-08-21 06:59:55 UTC

Parallelism

75/100

Blocked

46%

Avg conflicts / tx

1.38

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #97,843,808  ·  24 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xec7d120d…7084

0x34b655…2a6f

10 touches
10 conflicts

0x7753b200…57a7

0x34b655…2a6f

10 touches
10 conflicts

0xb3fb9fb5…64db

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0x8571fbdb…345a

0x34b655…2a6f

4 touches
1 conflict

0x17ce7874…0569

0x34b655…2a6f

4 touches
1 conflict

0x2528e717…2a22

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 0xec7d120df9…5d7084

← previous block·next block →recent activity