← previous blocknext block →recent activity

Analyzing

Block #98,081,165

31 transactions · 20 stateful · 2026-08-22 03:06:38 UTC

Parallelism

87/100

Blocked

30%

Avg conflicts / tx

0.35

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #98,081,165  ·  31 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

0x22e0cc1d…ad0d

0x34b655…2a6f

6 touches
3 conflicts

0xef8dd51a…259c

0x34b655…2a6f

6 touches
3 conflicts

0xca841faa…486a

0x34b655…2a6f

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

4 touches
1 conflict

0xef351445…5b12

0x34b655…2a6f

4 touches
1 conflict

0x24875ac2…7f46

0x34b655…2a6f

4 touches
1 conflict

0xd58b9a66…1c23

0x34b655…2a6f

4 touches
1 conflict

0x4dd2a831…bd5d

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

3 conflicts on slot 0x22e0cc1d4a…90ad0d

← previous block·next block →recent activity