← previous blocknext block →recent activity

Analyzing

Block #74,260,414

15 transactions · 12 stateful · 2026-05-13 05:49:59 UTC

Parallelism

73/100

Blocked

42%

Avg conflicts / tx

0.6

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,260,414  ·  15 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

0x28cc5685…bb83

0xd32edf…ff58

7 touches
6 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x18aed20c…48f3

0x000000…012a

2 touches
0 conflicts

0xf6802cf0…344f

0x000000…012a

2 touches
0 conflicts

0x00000000…0012

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…0013

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…0015

0x1b6862…e19c

2 touches
0 conflicts

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: 0xd32edf66…9fff58

6 conflicts on slot 0x28cc568576…4cbb83

← previous block·next block →recent activity