← previous blocknext block →recent activity

Analyzing

Block #98,217,144

19 transactions · 17 stateful · 2026-08-22 14:31:29 UTC

Parallelism

84/100

Blocked

35%

Avg conflicts / tx

0.37

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #98,217,144  ·  19 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

0xd66696e0…0842

0x34b655…2a6f

6 touches
3 conflicts

0x69162f69…9404

0x34b655…2a6f

6 touches
3 conflicts

0xc87e767e…4bba

0x34b655…2a6f

6 touches
3 conflicts

0x58edeb02…cfc5

0x34b655…2a6f

5 touches
3 conflicts

0xc824469a…641f

0x34b655…2a6f

4 touches
1 conflict

0x09e0690d…6e3d

0xe52b14…7230

4 touches
1 conflict

0x17bbe4f8…08c5

0xe52b14…7230

4 touches
1 conflict

0x3cebc8f1…975c

0xe52b14…7230

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 0xd66696e0dc…230842

← previous block·next block →recent activity