← previous blocknext block →recent activity

Analyzing

Block #98,581,368

23 transactions · 21 stateful · 2026-08-23 21:19:36 UTC

Parallelism

87/100

Blocked

29%

Avg conflicts / tx

0.26

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #98,581,368  ·  23 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x6fcdd294…5822

0x8964d7…10f8

4 touches
1 conflict

0x00000000…003d

0xa6afd3…d132

4 touches
1 conflict

0x6fcdd294…5827

0x8964d7…10f8

4 touches
1 conflict

0x6fcdd294…5826

0x8964d7…10f8

4 touches
1 conflict

0x889d5e90…929a

0x2a68ba…90c5

4 touches
1 conflict

0x19885029…5494

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

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: 0x8964d7c9…5b10f8

1 conflict on slot 0x6fcdd2946b…a65822

← previous block·next block →recent activity