← previous blocknext block →recent activity

Analyzing

Block #98,353,634

18 transactions · 18 stateful · 2026-08-23 01:58:10 UTC

Parallelism

72/100

Blocked

44%

Avg conflicts / tx

0.44

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #98,353,634  ·  18 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xed903df2…6ea4

0x34b655…2a6f

4 touches
1 conflict

0xfadc118d…5d64

0x34b655…2a6f

4 touches
1 conflict

0xfd7cbc61…c07d

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0xa6afd3…d132

4 touches
1 conflict

0x889d5e90…929a

0x2a68ba…90c5

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x631b4113…baa9

0x34b655…2a6f

4 touches
1 conflict

0x8f5fdd0a…6c4c

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 0xed903df2a7…046ea4

← previous block·next block →recent activity