← previous blocknext block →recent activity

Analyzing

Block #74,319,666

26 transactions · 19 stateful · 2026-05-13 12:24:11 UTC

Parallelism

73/100

Blocked

58%

Avg conflicts / tx

1.38

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #74,319,666  ·  26 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x00000000…0002

0xab3526…fa38

14 touches
21 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

12 touches
15 conflicts

0xc6417de0…2191

0xc8689a…ee79

6 touches
3 conflicts

0x14845934…d13c

0x34b655…2a6f

6 touches
3 conflicts

0x57de3828…3fbb

0x34b655…2a6f

6 touches
3 conflicts

0x8db1e0f2…2fcf

0x34b655…2a6f

6 touches
3 conflicts

0x9be2b99a…a959

0x34b655…2a6f

6 touches
3 conflicts

0xa91c899f…6ee3

0x34b655…2a6f

6 touches
3 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: 0xab35264b…1cfa38

21 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity