← previous blocknext block →recent activity

Analyzing

Block #98,320,903

21 transactions · 20 stateful · 2026-08-22 23:13:32 UTC

Parallelism

81/100

Blocked

40%

Avg conflicts / tx

0.67

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #98,320,903  ·  21 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x22e0cc1d…ad0d

0x34b655…2a6f

8 touches
6 conflicts

0xe23b2c29…6284

0x34b655…2a6f

6 touches
3 conflicts

0x71480e0a…7d12

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0xca841faa…486a

0x34b655…2a6f

6 touches
3 conflicts

0xa38c430a…e3cb

0x34b655…2a6f

4 touches
1 conflict

0xb7b16dd0…0426

0x34b655…2a6f

4 touches
1 conflict

0xd66696e0…0842

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 0x22e0cc1d4a…90ad0d

← previous block·next block →recent activity