← previous blocknext block →recent activity

Analyzing

Block #93,498,416

24 transactions · 16 stateful · 2026-08-06 01:09:37 UTC

Parallelism

88/100

Blocked

44%

Avg conflicts / tx

0.38

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #93,498,416  ·  24 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

0x6eb3e5af…064e

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x939bbb96…8556

0x34b655…2a6f

6 touches
3 conflicts

0xa0db8103…cccc

0xd32edf…ff58

5 touches
3 conflicts

0xa51de3df…c65a

0x34b655…2a6f

5 touches
3 conflicts

0x326a02b5…8dad

0x34b655…2a6f

4 touches
1 conflict

0x889d5e90…929a

0x2a68ba…90c5

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

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 0x6eb3e5af4f…78064e

← previous block·next block →recent activity