← previous blocknext block →recent activity

Analyzing

Block #74,609,346

18 transactions · 14 stateful · 2026-05-14 20:39:42 UTC

Parallelism

78/100

Blocked

29%

Avg conflicts / tx

0.39

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,609,346  ·  18 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xadac4a86…c2bc

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0xbc04d98e…a484

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0001

0x75c3ab…4f0d

4 touches
1 conflict

0x3ba34a4e…a580

0x34b655…2a6f

4 touches
1 conflict

0x5593214e…dfc1

0x3bd359…433a

4 touches
1 conflict

0xa472d565…9fe4

0x3bd359…433a

4 touches
1 conflict

0x44ad89ba…cf83

0x5e1b1a…7777

4 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: 0x34b6552d…112a6f

6 conflicts on slot 0xadac4a860c…a3c2bc

← previous block·next block →recent activity