← previous blocknext block →recent activity

Analyzing

Block #74,439,354

19 transactions · 15 stateful · 2026-05-14 01:40:39 UTC

Parallelism

74/100

Blocked

33%

Avg conflicts / tx

0.58

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,439,354  ·  19 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

0x6ca2850d…6d1b

0xd32edf…ff58

9 touches
10 conflicts

0x99f666e3…b2a2

0x3bd359…433a

4 touches
1 conflict

0x9194f4a3…10b8

0x754704…b603

4 touches
1 conflict

0x00000000…0000

0xfa32f9…f3f0

4 touches
1 conflict

0x00000000…0001

0xfa32f9…f3f0

4 touches
1 conflict

0xe90b7bce…c2e0

0xfa32f9…f3f0

4 touches
1 conflict

0x00000000…0006

0x010592…1c83

2 touches
0 conflicts

0x62b7c59f…e55d

0x010592…1c83

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

10 conflicts on slot 0x6ca2850dbe…716d1b

← previous block·next block →recent activity