← previous blocknext block →recent activity

Analyzing

Block #74,458,654

17 transactions · 14 stateful · 2026-05-14 03:49:09 UTC

Parallelism

71/100

Blocked

43%

Avg conflicts / tx

0.76

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,458,654  ·  17 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

10 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x62d080e9…4a7c

0x34b655…2a6f

6 touches
3 conflicts

0x7cbd466f…1700

0x34b655…2a6f

4 touches
1 conflict

0x874f5c70…608f

0x34b655…2a6f

4 touches
1 conflict

0xc0f25d9d…67d1

0x34b655…2a6f

4 touches
1 conflict

0xde3a7f3a…8480

0x34b655…2a6f

4 touches
1 conflict

0x37d49489…9309

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

10 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity