← previous blocknext block →recent activity

Analyzing

Block #98,438,598

19 transactions · 19 stateful · 2026-08-23 09:05:38 UTC

Parallelism

89/100

Blocked

26%

Avg conflicts / tx

0.26

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #98,438,598  ·  19 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

0xbcbf5d09…8bac

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x6ca0994e…02ef

0x34b655…2a6f

4 touches
1 conflict

0x6f32a04c…0e17

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0xa6afd3…d132

4 touches
1 conflict

0x88ecacda…04c9

0xa6afd3…d132

4 touches
1 conflict

0x00000000…0002

0xbb3f3c…e046

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 0xbcbf5d09a8…c68bac

← previous block·next block →recent activity