← previous blocknext block →recent activity

Analyzing

Block #74,433,336

23 transactions · 21 stateful · 2026-05-14 01:00:37 UTC

Parallelism

57/100

Blocked

62%

Avg conflicts / tx

2.22

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #74,433,336  ·  23 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0xdea4ea06…3c94

0xd32edf…ff58

19 touches
45 conflicts

0x00000000…001b

0x1b6862…e19c

6 touches
3 conflicts

0x24968e6d…0132

0x065c9d…c394

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…002b

0x1b6862…e19c

6 touches
3 conflicts

0xba5743c7…21c2

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

45 conflicts on slot 0xdea4ea06d7…d83c94

← previous block·next block →recent activity