← previous blocknext block →recent activity

Analyzing

Block #98,417,585

15 transactions · 15 stateful · 2026-08-23 07:19:55 UTC

Parallelism

73/100

Blocked

53%

Avg conflicts / tx

1.13

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #98,417,585  ·  15 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

0x710f49c8…ed34

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x7de57974…f5ba

0x34b655…2a6f

6 touches
3 conflicts

0xb903ef62…6328

0x34b655…2a6f

6 touches
3 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

6 touches
3 conflicts

0x5cfbeb21…92b1

0x34b655…2a6f

6 touches
3 conflicts

0xef048f92…572b

0x34b655…2a6f

4 touches
1 conflict

0x326a02b5…8dad

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

3 conflicts on slot 0x710f49c81e…a5ed34

← previous block·next block →recent activity