← previous blocknext block →recent activity

Analyzing

Block #98,263,517

19 transactions · 17 stateful · 2026-08-22 18:24:46 UTC

Parallelism

89/100

Blocked

18%

Avg conflicts / tx

0.16

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #98,263,517  ·  19 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

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x705a9a1a…db08

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0x00000000…0007

0x340143…768f

4 touches
1 conflict

0x00000000…0002

0x064fb5…6207

2 touches
0 conflicts

0x00000000…0008

0x064fb5…6207

2 touches
0 conflicts

0x3f1434d4…1ce1

0x11ed3b…2c96

2 touches
0 conflicts

0xfd4df3d8…23fe

0x11ed3b…2c96

2 touches
0 conflicts

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 0x482471adbb…39122f

← previous block·next block →recent activity