← previous blocknext block →recent activity

Analyzing

Block #74,454,946

18 transactions · 17 stateful · 2026-05-14 03:24:26 UTC

Parallelism

56/100

Blocked

47%

Avg conflicts / tx

1.61

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #74,454,946  ·  18 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

0x00c46468…f328

0x3bd359…433a

16 touches
28 conflicts

0x00000000…0001

0xcc67aa…c71c

16 touches
28 conflicts

0x00000000…0000

0xcc67aa…c71c

16 touches
28 conflicts

0xce2b6650…ecc3

0x5c2513…7777

16 touches
28 conflicts

0x44ad89ba…cf83

0x5c2513…7777

16 touches
28 conflicts

0xa472d565…9fe4

0x3bd359…433a

16 touches
28 conflicts

0xeedf1667…51e4

0x34b655…2a6f

4 touches
1 conflict

0x1c389468…6b0e

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: 0x3bd359c1…15433a

28 conflicts on slot 0x00c46468d1…54f328

← previous block·next block →recent activity