← previous blocknext block →recent activity

Analyzing

Block #98,491,943

21 transactions · 19 stateful · 2026-08-23 13:34:22 UTC

Parallelism

71/100

Blocked

37%

Avg conflicts / tx

0.71

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #98,491,943  ·  21 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

0xca841faa…486a

0x34b655…2a6f

8 touches
6 conflicts

0xe5bb3628…e5f1

0x34b655…2a6f

8 touches
6 conflicts

0xe62e1553…ed4b

0x34b655…2a6f

6 touches
3 conflicts

0x152a2f3e…13f8

0x34b655…2a6f

6 touches
3 conflicts

0x4c1c61eb…6992

0x34b655…2a6f

4 touches
1 conflict

0x4ccfe55c…de03

0x34b655…2a6f

4 touches
1 conflict

0x58620f29…db5a

0x34b655…2a6f

4 touches
1 conflict

0x68c07cb9…ae14

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 0xca841faae5…71486a

← previous block·next block →recent activity