← previous blocknext block →recent activity

Analyzing

Block #98,217,309

17 transactions · 17 stateful · 2026-08-22 14:32:19 UTC

Parallelism

71/100

Blocked

41%

Avg conflicts / tx

0.71

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #98,217,309  ·  17 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

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0xdfac3ce0…6699

0x99c7a7…8bf0

4 touches
1 conflict

0x0eff0903…8165

0x754704…b603

4 touches
1 conflict

0x777c9106…162a

0x754704…b603

4 touches
1 conflict

0x68c08dd2…be14

0x99c7a7…8bf0

4 touches
1 conflict

0x00000000…0007

0x340143…768f

4 touches
1 conflict

0x1fd77335…9120

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

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

6 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity