← previous blocknext block →recent activity

Analyzing

Block #98,414,352

30 transactions · 25 stateful · 2026-08-23 07:03:39 UTC

Parallelism

77/100

Blocked

52%

Avg conflicts / tx

1.27

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #98,414,352  ·  30 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x00000000…0002

0xbb3f3c…e046

14 touches
21 conflicts

0xbde524f4…43bf

0x34b655…2a6f

10 touches
10 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0x705ab4ae…0162

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x10f0a1bf…12c3

0x34b655…2a6f

6 touches
3 conflicts

0x682e1d93…b8fb

0x34b655…2a6f

5 touches
3 conflicts

0x00000000…002b

0x1b6862…e19c

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: 0xbb3f3cb7…74e046

21 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity