← previous blocknext block →recent activity

Analyzing

Block #73,476,138

14 transactions · 13 stateful · 2026-05-09 14:32:34 UTC

Parallelism

50/100

Blocked

46%

Avg conflicts / tx

1.5

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #73,476,138  ·  14 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

0xae3fbd28…a18c

0x3bd359…433a

14 touches
21 conflicts

0xbc467e7a…af36

0x21e325…7777

14 touches
21 conflicts

0x00000000…0000

0xe5a8f8…d7a8

14 touches
21 conflicts

0x00000000…0002

0xe5a8f8…d7a8

14 touches
21 conflicts

0x00000000…0003

0xe5a8f8…d7a8

14 touches
21 conflicts

0x13377d75…4720

0x065c9d…c394

2 touches
0 conflicts

0x209c57e0…4524

0x065c9d…c394

2 touches
0 conflicts

0x3c318496…9f15

0x21e325…7777

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

21 conflicts on slot 0xae3fbd28fa…e7a18c

← previous block·next block →recent activity