← previous blocknext block →recent activity

Analyzing

Block #74,436,566

35 transactions · 27 stateful · 2026-05-14 01:22:05 UTC

Parallelism

86/100

Blocked

63%

Avg conflicts / tx

0.89

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,436,566  ·  35 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xadac4a86…c2bc

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…0002

0xab3526…fa38

8 touches
6 conflicts

0xc29d33c0…c883

0xd32edf…ff58

7 touches
6 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…001b

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…002b

0x1b6862…e19c

6 touches
3 conflicts

0x17a7f697…dcb4

0x1b6862…e19c

6 touches
3 conflicts

0xd9f18d9a…141d

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: 0x34b6552d…112a6f

6 conflicts on slot 0xadac4a860c…a3c2bc

← previous block·next block →recent activity