← previous blocknext block →recent activity

Analyzing

Block #74,607,463

28 transactions · 21 stateful · 2026-05-14 20:27:09 UTC

Parallelism

79/100

Blocked

43%

Avg conflicts / tx

0.68

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #74,607,463  ·  28 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

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0xa91c899f…6ee3

0x34b655…2a6f

6 touches
3 conflicts

0x24968e6d…0132

0x065c9d…c394

6 touches
3 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0xca3b1c25…b2d7

0xd32edf…ff58

5 touches
3 conflicts

0xcb45d9d6…cb87

0x1b6862…e19c

4 touches
1 conflict

0x1fcacf75…7ade

0x34b655…2a6f

4 touches
1 conflict

0x3b3a5945…10d0

0x34b655…2a6f

4 touches
1 conflict

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity