← previous blocknext block →recent activity

Analyzing

Block #74,409,518

30 transactions · 19 stateful · 2026-05-13 22:22:04 UTC

Parallelism

73/100

Blocked

53%

Avg conflicts / tx

1.17

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #74,409,518  ·  30 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x6d438f40…4382

0xd32edf…ff58

15 touches
28 conflicts

0x00000000…0002

0x116e7d…d8f1

8 touches
6 conflicts

0xb7143610…adc4

0x3bd359…433a

8 touches
6 conflicts

0x692a4122…76b8

0x350035…7777

8 touches
6 conflicts

0x00000000…0003

0x116e7d…d8f1

8 touches
6 conflicts

0x00000000…0000

0x116e7d…d8f1

8 touches
6 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0012

0x1b6862…e19c

6 touches
3 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

28 conflicts on slot 0x6d438f4092…fe4382

← previous block·next block →recent activity