← previous blocknext block →recent activity

Analyzing

Block #74,241,036

17 transactions · 14 stateful · 2026-05-13 03:41:14 UTC

Parallelism

59/100

Blocked

57%

Avg conflicts / tx

1.35

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #74,241,036  ·  17 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x07d70afb…360c

0xd32edf…ff58

13 touches
21 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x826cce18…251c

0x34b655…2a6f

4 touches
1 conflict

0xa159517d…d8d0

0x1001ff…1001

2 touches
0 conflicts

0xc6f1b3af…c97c

0x1001ff…1001

2 touches
0 conflicts

0x00000000…0012

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…0013

0x1b6862…e19c

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

21 conflicts on slot 0x07d70afbda…e5360c

← previous block·next block →recent activity