← previous blocknext block →recent activity

Analyzing

Block #98,648,420

15 transactions · 15 stateful · 2026-08-24 03:08:38 UTC

Parallelism

80/100

Blocked

33%

Avg conflicts / tx

0.47

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #98,648,420  ·  15 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x45de70d9…e1dc

0x34b655…2a6f

6 touches
3 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

4 touches
1 conflict

0x6cb5409a…dcb3

0x34b655…2a6f

4 touches
1 conflict

0x82c5589e…5b89

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0xd66696e0…0842

0x34b655…2a6f

4 touches
1 conflict

0xfe888b58…0411

0x34b655…2a6f

4 touches
1 conflict

0x30d3b573…4288

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 0x45de70d9be…64e1dc

← previous block·next block →recent activity