← previous blocknext block →recent activity

Analyzing

Block #74,434,625

22 transactions · 15 stateful · 2026-05-14 01:09:12 UTC

Parallelism

64/100

Blocked

47%

Avg conflicts / tx

1.27

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #74,434,625  ·  22 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0xbc9b6507…5dcd

0xd32edf…ff58

15 touches
28 conflicts

0x00000000…001b

0x1b6862…e19c

4 touches
1 conflict

0xba5743c7…21c2

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0xbcc1b459…f94f

0x3bd359…433a

4 touches
1 conflict

0xa74cd79c…705a

0x405b63…7777

4 touches
1 conflict

0x00000000…0000

0xaa5de1…d330

4 touches
1 conflict

0x00000000…0001

0xaa5de1…d330

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: 0xd32edf66…9fff58

28 conflicts on slot 0xbc9b6507fb…6c5dcd

← previous block·next block →recent activity