← previous blocknext block →recent activity

Analyzing

Block #74,774,017

19 transactions · 13 stateful · 2026-05-15 14:58:57 UTC

Parallelism

84/100

Blocked

23%

Avg conflicts / tx

0.21

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,774,017  ·  19 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

0x6d49cec1…211d

0xd32edf…ff58

5 touches
3 conflicts

0x00c46468…f328

0x3bd359…433a

4 touches
1 conflict

0xa472d565…9fe4

0x3bd359…433a

4 touches
1 conflict

0x44ad89ba…cf83

0x5c2513…7777

4 touches
1 conflict

0xce2b6650…ecc3

0x5c2513…7777

4 touches
1 conflict

0x00000000…0000

0xcc67aa…c71c

4 touches
1 conflict

0x00000000…0001

0xcc67aa…c71c

4 touches
1 conflict

0x10f5f4d8…572e

0x34b655…2a6f

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 0x6d49cec198…30211d

← previous block·next block →recent activity