← previous blocknext block →recent activity

Analyzing

Block #74,626,057

22 transactions · 13 stateful · 2026-05-14 22:31:07 UTC

Parallelism

73/100

Blocked

46%

Avg conflicts / tx

0.73

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #74,626,057  ·  22 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xf9f2761a…32c6

0xd32edf…ff58

11 touches
15 conflicts

0x70e01664…d9d5

0x065c9d…c394

4 touches
1 conflict

0x4e7eb462…b2b1

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x00000000…0013

0x1b6862…e19c

4 touches
1 conflict

0x59bf920c…3c0b

0x065c9d…c394

3 touches
1 conflict

0xcc45db1e…9843

0x065c9d…c394

3 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

15 conflicts on slot 0xf9f2761a3c…6c32c6

← previous block·next block →recent activity