← previous blocknext block →recent activity

Analyzing

Block #98,418,363

22 transactions · 21 stateful · 2026-08-23 07:23:50 UTC

Parallelism

59/100

Blocked

48%

Avg conflicts / tx

1.77

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #98,418,363  ·  22 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0x482471ad…122f

0x34b655…2a6f

18 touches
36 conflicts

0xc824469a…6425

0x34b655…2a6f

16 touches
28 conflicts

0xbde524f4…43bf

0x34b655…2a6f

8 touches
6 conflicts

0x705ab4ae…0162

0x34b655…2a6f

7 touches
6 conflicts

0xe5bb3628…e5f1

0x34b655…2a6f

6 touches
3 conflicts

0xe4af4c87…9964

0x34b655…2a6f

6 touches
3 conflicts

0x97996945…45b8

0x34b655…2a6f

5 touches
3 conflicts

0x6cff9ca3…2137

0x34b655…2a6f

5 touches
3 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

36 conflicts on slot 0x482471adbb…39122f

← previous block·next block →recent activity