← previous blocknext block →recent activity

Analyzing

Block #98,063,445

18 transactions · 16 stateful · 2026-08-22 01:37:27 UTC

Parallelism

83/100

Blocked

31%

Avg conflicts / tx

0.33

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #98,063,445  ·  18 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xf3d10975…0d07

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x40c49f…2af0

4 touches
1 conflict

0x065ff70b…356d

0x40c49f…2af0

4 touches
1 conflict

0x3f81bcfb…2905

0x40c49f…2af0

4 touches
1 conflict

0x6114e911…0b98

0x40c49f…2af0

4 touches
1 conflict

0xd060546b…e8c2

0x40c49f…2af0

4 touches
1 conflict

0x00000000…0007

0x340143…768f

4 touches
1 conflict

0x2bd1c200…56de

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

1 conflict on slot 0xf3d10975b0…050d07

← previous block·next block →recent activity