← previous blocknext block →recent activity

Analyzing

Block #98,913,260

17 transactions · 16 stateful · 2026-08-25 01:30:14 UTC

Parallelism

88/100

Blocked

25%

Avg conflicts / tx

0.29

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #98,913,260  ·  17 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

0xfb682e7d…dde9

0x34b655…2a6f

4 touches
1 conflict

0x25f2ab64…f456

0x40c49f…2af0

4 touches
1 conflict

0xc9dbd3c7…ac9f

0x40c49f…2af0

4 touches
1 conflict

0x556a9a7a…b0ae

0x34b655…2a6f

4 touches
1 conflict

0x63a8652c…5b43

0x34b655…2a6f

4 touches
1 conflict

0x63a8652c…5b44

0x34b655…2a6f

4 touches
1 conflict

0x6474161a…6a37

0x34b655…2a6f

4 touches
1 conflict

0x70d81211…f49f

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 0xfb682e7d8c…dcdde9

← previous block·next block →recent activity