← previous blocknext block →recent activity

Analyzing

Block #74,436,482

23 transactions · 17 stateful · 2026-05-14 01:21:32 UTC

Parallelism

65/100

Blocked

47%

Avg conflicts / tx

1.39

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #74,436,482  ·  23 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

0x024b1c08…e0fe

0xd32edf…ff58

15 touches
28 conflicts

0x765c236f…ff45

0x2a68ba…90c5

8 touches
6 conflicts

0x23a6209f…e00c

0x065c9d…c394

7 touches
6 conflicts

0x00000000…002b

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0012

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…001b

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 0x024b1c0828…f3e0fe

← previous block·next block →recent activity