← previous blocknext block →recent activity

Analyzing

Block #98,652,669

29 transactions · 23 stateful · 2026-08-24 03:30:47 UTC

Parallelism

86/100

Blocked

26%

Avg conflicts / tx

0.28

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #98,652,669  ·  29 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

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0xe5bb3628…e5f1

0x34b655…2a6f

4 touches
1 conflict

0xca841faa…486a

0x34b655…2a6f

4 touches
1 conflict

0x09106a95…1467

0x33176b…e078

4 touches
1 conflict

0x0a809ce1…7894

0x34b655…2a6f

4 touches
1 conflict

0x81ceb686…4df3

0x34b655…2a6f

4 touches
1 conflict

0x86cea35b…bdff

0x34b655…2a6f

4 touches
1 conflict

0x95d27c5a…4591

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

← previous block·next block →recent activity