← previous blocknext block →recent activity

Analyzing

Block #74,586,149

26 transactions · 21 stateful · 2026-05-14 18:04:11 UTC

Parallelism

77/100

Blocked

62%

Avg conflicts / tx

1.19

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #74,586,149  ·  26 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x566d68e8…439c

0xd32edf…ff58

11 touches
15 conflicts

0xbad68552…e6bf

0x34b655…2a6f

10 touches
10 conflicts

0xea02471d…1542

0x34b655…2a6f

10 touches
10 conflicts

0x00000000…0013

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0015

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…001e

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…002e

0x1b6862…e19c

8 touches
6 conflicts

0xd25997d0…a689

0x1b6862…e19c

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

15 conflicts on slot 0x566d68e8bf…01439c

← previous block·next block →recent activity