← previous blocknext block →recent activity

Analyzing

Block #98,027,209

22 transactions · 17 stateful · 2026-08-21 22:35:07 UTC

Parallelism

82/100

Blocked

35%

Avg conflicts / tx

0.41

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #98,027,209  ·  22 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xac396ef5…4953

0x065c9d…c394

4 touches
1 conflict

0x00000000…0007

0x340143…768f

4 touches
1 conflict

0x00000000…003d

0xa6afd3…d132

4 touches
1 conflict

0xadbda1a7…5f21

0xa6afd3…d132

4 touches
1 conflict

0xf88ccd07…a684

0xa6afd3…d132

4 touches
1 conflict

0xf6cc7de8…0b4a

0x3bd359…433a

2 touches
0 conflicts

0x09000000…0001

0x000000…1000

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

6 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity