← previous blocknext block →recent activity

Analyzing

Block #74,355,311

14 transactions · 13 stateful · 2026-05-13 16:21:11 UTC

Parallelism

71/100

Blocked

38%

Avg conflicts / tx

0.64

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,355,311  ·  14 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

0xa472d565…9fe4

0x3bd359…433a

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x9e719c7a…df63

0x34b655…2a6f

6 touches
3 conflicts

0x8c49c85c…ee96

0x34b655…2a6f

6 touches
3 conflicts

0xc44a43c5…a54b

0x34b655…2a6f

6 touches
3 conflicts

0x00c46468…f328

0x3bd359…433a

4 touches
1 conflict

0x5593214e…dfc1

0x3bd359…433a

4 touches
1 conflict

0x44ad89ba…cf83

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

6 conflicts on slot 0xa472d565a0…ae9fe4

← previous block·next block →recent activity