← previous blocknext block →recent activity

Analyzing

Block #74,453,142

30 transactions · 21 stateful · 2026-05-14 03:12:22 UTC

Parallelism

73/100

Blocked

48%

Avg conflicts / tx

1.13

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #74,453,142  ·  30 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

0x00000000…0002

0xab3526…fa38

16 touches
28 conflicts

0x99a3a7c1…1e2b

0x0cc9b2…7777

8 touches
6 conflicts

0x00000000…0000

0x019883…2a9a

8 touches
6 conflicts

0x44ad89ba…cf83

0x0cc9b2…7777

8 touches
6 conflicts

0xa472d565…9fe4

0x3bd359…433a

8 touches
6 conflicts

0x00000000…0002

0x019883…2a9a

8 touches
6 conflicts

0xa10c86f8…4b74

0x3bd359…433a

8 touches
6 conflicts

0x00000000…0015

0x1b6862…e19c

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

28 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity