← previous blocknext block →recent activity

Analyzing

Block #97,546,646

19 transactions · 19 stateful · 2026-08-20 05:49:49 UTC

Parallelism

74/100

Blocked

37%

Avg conflicts / tx

0.68

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #97,546,646  ·  19 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0x482471ad…122f

0x34b655…2a6f

8 touches
6 conflicts

0xb97c885b…2933

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x0df13365…7c52

0x34b655…2a6f

4 touches
1 conflict

0x1c4f114f…2abd

0x34b655…2a6f

4 touches
1 conflict

0x1e18acb1…a40a

0x34b655…2a6f

4 touches
1 conflict

0x35b89cd8…5092

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 0xc824469a90…af6425

← previous block·next block →recent activity