← previous blocknext block →recent activity

Analyzing

Block #74,433,404

17 transactions · 14 stateful · 2026-05-14 01:01:04 UTC

Parallelism

76/100

Blocked

29%

Avg conflicts / tx

0.41

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,433,404  ·  17 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

0x4b5e135d…3c20

0xd32edf…ff58

7 touches
6 conflicts

0x00000000…0000

0xba6585…ec37

4 touches
1 conflict

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x405dd86b…076b

0x065c9d…c394

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

0x00000000…001b

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 0x4b5e135d0c…e73c20

← previous block·next block →recent activity