← previous blocknext block →recent activity

Analyzing

Block #98,263,789

13 transactions · 13 stateful · 2026-08-22 18:26:08 UTC

Parallelism

69/100

Blocked

23%

Avg conflicts / tx

0.23

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #98,263,789  ·  13 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

4 touches
1 conflict

0xbde524f4…43bf

0x34b655…2a6f

4 touches
1 conflict

0xea57afd0…4232

0x34b655…2a6f

4 touches
1 conflict

0x085df2c1…305a

0x34b655…2a6f

2 touches
0 conflicts

0x14cc77c7…69c4

0x34b655…2a6f

2 touches
0 conflicts

0x5451de01…be8e

0x34b655…2a6f

2 touches
0 conflicts

0x5a7d6ae7…8f82

0x34b655…2a6f

2 touches
0 conflicts

0x711ceb8d…5202

0x34b655…2a6f

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity