← previous blocknext block →recent activity

Analyzing

Block #98,766,290

24 transactions · 22 stateful · 2026-08-24 13:10:37 UTC

Parallelism

88/100

Blocked

27%

Avg conflicts / tx

0.29

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #98,766,290  ·  24 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xd6d040d9…9ae3

0x34b655…2a6f

4 touches
1 conflict

0xfadc118d…5d64

0x34b655…2a6f

4 touches
1 conflict

0xed4cf5a9…f734

0x34b655…2a6f

4 touches
1 conflict

0xea02471d…1542

0x34b655…2a6f

4 touches
1 conflict

0x889d5e90…929a

0x2a68ba…90c5

4 touches
1 conflict

0x00000000…00c9

0x34b655…2a6f

4 touches
1 conflict

0x3996c88c…85c0

0x34b655…2a6f

4 touches
1 conflict

0x44aded65…ab30

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 0xd6d040d989…9c9ae3

← previous block·next block →recent activity