← previous blocknext block →recent activity

Analyzing

Block #74,764,838

21 transactions · 16 stateful · 2026-05-15 13:57:25 UTC

Parallelism

81/100

Blocked

38%

Avg conflicts / tx

0.48

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,764,838  ·  21 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

0x388e001a…7e04

0x34b655…2a6f

6 touches
3 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0x870a0f81…b352

0xd32edf…ff58

5 touches
3 conflicts

0x57de3828…3fbb

0x34b655…2a6f

4 touches
1 conflict

0x00000000…000b

0x1d6533…307c

4 touches
1 conflict

0x36cdae67…8407

0x34b655…2a6f

4 touches
1 conflict

0x8db1e0f2…2fcf

0x34b655…2a6f

4 touches
1 conflict

0x9be2b99a…a959

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 0x388e001a16…e57e04

← previous block·next block →recent activity