← previous blocknext block →recent activity

Analyzing

Block #93,074,928

23 transactions · 19 stateful · 2026-08-04 13:39:34 UTC

Parallelism

83/100

Blocked

37%

Avg conflicts / tx

0.39

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #93,074,928  ·  23 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x840d3ab7…c8c4

0x34b655…2a6f

6 touches
3 conflicts

0xca841faa…486a

0x34b655…2a6f

6 touches
3 conflicts

0x244fd0dc…ddcc

0x34b655…2a6f

4 touches
1 conflict

0x2b856d86…7988

0x34b655…2a6f

4 touches
1 conflict

0x30c5329c…711c

0x34b655…2a6f

4 touches
1 conflict

0x3377da70…01e5

0x34b655…2a6f

4 touches
1 conflict

0x38bdc5d3…a632

0x34b655…2a6f

4 touches
1 conflict

0x4ae3b148…7ed2

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 0x840d3ab7c3…edc8c4

← previous block·next block →recent activity