← previous blocknext block →recent activity

Analyzing

Block #98,490,826

29 transactions · 24 stateful · 2026-08-23 13:28:45 UTC

Parallelism

79/100

Blocked

25%

Avg conflicts / tx

0.48

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #98,490,826  ·  29 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xac2a0273…721b

0x34b655…2a6f

8 touches
6 conflicts

0x737acb78…fce8

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xfe45073e…6315

0x34b655…2a6f

6 touches
3 conflicts

0x71fad9ce…c11f

0x34b655…2a6f

6 touches
3 conflicts

0x62910921…3016

0x34b655…2a6f

4 touches
1 conflict

0xe2815a10…3c44

0x34b655…2a6f

4 touches
1 conflict

0x856d2776…04c9

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 0xac2a02739b…81721b

← previous block·next block →recent activity