← previous blocknext block →recent activity

Analyzing

Block #98,575,289

17 transactions · 15 stateful · 2026-08-23 20:48:06 UTC

Parallelism

88/100

Blocked

20%

Avg conflicts / tx

0.18

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #98,575,289  ·  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

0xf25329b7…e70e

0x34b655…2a6f

4 touches
1 conflict

0x5311f864…0984

0x754704…b603

4 touches
1 conflict

0x4a6a68b5…f8b8

0x928dc8…8207

4 touches
1 conflict

0x4a6a68b5…f8bb

0x928dc8…8207

4 touches
1 conflict

0x4a6a68b5…f8bc

0x928dc8…8207

4 touches
1 conflict

0x009537a5…e2f6

0x34b655…2a6f

4 touches
1 conflict

0x28fe17d2…4cc0

0x34b655…2a6f

4 touches
1 conflict

0x40b05922…95a4

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 0xf25329b71c…50e70e

← previous block·next block →recent activity