← previous blocknext block →recent activity

Analyzing

Block #74,419,199

16 transactions · 13 stateful · 2026-05-13 23:26:26 UTC

Parallelism

81/100

Blocked

38%

Avg conflicts / tx

0.44

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,419,199  ·  16 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x851866f8…38d2

0xd32edf…ff58

5 touches
3 conflicts

0x3d6ad949…c225

0x34b655…2a6f

4 touches
1 conflict

0xa3ff1ab2…8ae3

0x34b655…2a6f

4 touches
1 conflict

0xbed60ae3…a19c

0x34b655…2a6f

4 touches
1 conflict

0xfe3d37ee…6e67

0x34b655…2a6f

4 touches
1 conflict

0x00000000…0002

0xab3526…fa38

4 touches
1 conflict

0x35b65947…44d1

0xc8689a…ee79

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

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

3 conflicts on slot 0x851866f8a7…a738d2

← previous block·next block →recent activity