← previous blocknext block →recent activity

Analyzing

Block #74,409,434

24 transactions · 22 stateful · 2026-05-13 22:21:30 UTC

Parallelism

58/100

Blocked

64%

Avg conflicts / tx

2.33

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #74,409,434  ·  24 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

0x00000000…0002

0xab3526…fa38

20 touches
45 conflicts

0xa472d565…9fe4

0x3bd359…433a

10 touches
10 conflicts

0x44ad89ba…cf83

0x0cc9b2…7777

10 touches
10 conflicts

0x00000000…0002

0x019883…2a9a

10 touches
10 conflicts

0x00000000…0000

0x019883…2a9a

10 touches
10 conflicts

0xa10c86f8…4b74

0x3bd359…433a

10 touches
10 conflicts

0x99a3a7c1…1e2b

0x0cc9b2…7777

10 touches
10 conflicts

0xfa2527aa…9dd5

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: 0xab35264b…1cfa38

45 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity