← previous blocknext block →recent activity

Analyzing

Block #74,429,954

36 transactions · 25 stateful · 2026-05-14 00:38:01 UTC

Parallelism

89/100

Blocked

32%

Avg conflicts / tx

0.33

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,429,954  ·  36 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xa5516069…f81a

0xd32edf…ff58

7 touches
6 conflicts

0xd77e90ec…8c04

0x3bd359…433a

6 touches
3 conflicts

0xd6aabe89…92f5

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x00000000…0004

0xd5b70d…615b

4 touches
1 conflict

0x18aed20c…48f3

0x000000…012a

4 touches
1 conflict

0x00000000…0004

0x63e48b…53f2

4 touches
1 conflict

0x08943ea2…ed03

0x754704…b603

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

6 conflicts on slot 0xa5516069ba…1ef81a

← previous block·next block →recent activity