← previous blocknext block →recent activity

Analyzing

Block #98,096,679

19 transactions · 19 stateful · 2026-08-22 04:24:41 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,096,679  ·  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

0x261cbea7…e35e

0x34b655…2a6f

4 touches
1 conflict

0xd17580f9…ece1

0x754704…b603

4 touches
1 conflict

0xca841faa…486a

0x34b655…2a6f

4 touches
1 conflict

0x00000000…0007

0x340143…768f

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x72b8cf87…b940

0x40c49f…2af0

2 touches
0 conflicts

0xa0f21917…1e9f

0x40c49f…2af0

2 touches
0 conflicts

0x0b552eae…fbd9

0x754704…b603

2 touches
0 conflicts

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 0x261cbea79d…12e35e

← previous block·next block →recent activity