← previous blocknext block →recent activity

Analyzing

Block #98,531,824

17 transactions · 15 stateful · 2026-08-23 17:01:15 UTC

Parallelism

88/100

Blocked

13%

Avg conflicts / tx

0.12

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #98,531,824  ·  17 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0xf56d5d0e…222c

0x34b655…2a6f

4 touches
1 conflict

0x17c93766…889e

0x34b655…2a6f

4 touches
1 conflict

0x6e3e9f18…f684

0x34b655…2a6f

4 touches
1 conflict

0x7e5ea60a…c4aa

0x34b655…2a6f

4 touches
1 conflict

0x886db264…846e

0x34b655…2a6f

4 touches
1 conflict

0x92385428…6941

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x5fee7566…b8fd

0x34b655…2a6f

3 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

1 conflict on slot 0xf56d5d0ea8…dc222c

← previous block·next block →recent activity