← previous blocknext block →recent activity

Analyzing

Block #74,427,286

16 transactions · 13 stateful · 2026-05-14 00:20:17 UTC

Parallelism

81/100

Blocked

31%

Avg conflicts / tx

0.31

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,427,286  ·  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

0x89279c27…fd70

0xd32edf…ff58

5 touches
3 conflicts

0xbad68552…e6bf

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x8f478f26…9d56

0x000000…012a

2 touches
0 conflicts

0x9cafc3b6…ee8c

0x000000…012a

2 touches
0 conflicts

0x00000000…0036

0x386489…7508

2 touches
0 conflicts

0x1a920eda…bfae

0x386489…7508

2 touches
0 conflicts

0x15bae5fc…9f7e

0x57ea24…2cec

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

3 conflicts on slot 0x89279c277f…32fd70

← previous block·next block →recent activity