← previous blocknext block →recent activity

Analyzing

Block #74,462,613

19 transactions · 12 stateful · 2026-05-14 04:15:30 UTC

Parallelism

89/100

Blocked

17%

Avg conflicts / tx

0.11

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,462,613  ·  19 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x00c46468…f328

0x3bd359…433a

4 touches
1 conflict

0x44ad89ba…cf83

0x5c2513…7777

4 touches
1 conflict

0xce2b6650…ecc3

0x5c2513…7777

4 touches
1 conflict

0xa472d565…9fe4

0x3bd359…433a

4 touches
1 conflict

0x30276c1c…47b4

0x2a68ba…90c5

4 touches
1 conflict

0x00000000…0000

0xcc67aa…c71c

4 touches
1 conflict

0x00000000…0001

0xcc67aa…c71c

4 touches
1 conflict

0x1c674c1d…a7a3

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: 0x3bd359c1…15433a

1 conflict on slot 0x00c46468d1…54f328

← previous block·next block →recent activity