← previous blocknext block →recent activity

Analyzing

Block #97,517,933

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

Parallelism

89/100

Blocked

36%

Avg conflicts / tx

0.28

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #97,517,933  ·  18 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x737acb78…fce8

0x34b655…2a6f

4 touches
1 conflict

0x845ec8b0…c1af

0x34b655…2a6f

4 touches
1 conflict

0x2c67324f…a492

0x34b655…2a6f

4 touches
1 conflict

0x9ad325f5…cc43

0x34b655…2a6f

4 touches
1 conflict

0xac2a0273…721b

0x34b655…2a6f

4 touches
1 conflict

0xbde524f4…43bf

0x34b655…2a6f

4 touches
1 conflict

0x00000000…004b

0x80c745…7210

4 touches
1 conflict

0x00000000…004c

0x80c745…7210

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

1 conflict on slot 0x737acb7813…fafce8

← previous block·next block →recent activity