← previous blocknext block →recent activity

Analyzing

Block #73,867,401

16 transactions · 16 stateful · 2026-05-11 10:12:34 UTC

Parallelism

63/100

Blocked

56%

Avg conflicts / tx

1.63

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,867,401  ·  16 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

0x765c236f…ff45

0x2a68ba…90c5

12 touches
15 conflicts

0x89a9b173…222c

0xd32edf…ff58

9 touches
10 conflicts

0x9faba0be…eaa5

0x065c9d…c394

7 touches
6 conflicts

0x00000000…0004

0xd5b70d…615b

6 touches
3 conflicts

0x18aed20c…48f3

0x000000…012a

6 touches
3 conflicts

0x7c403af1…31b1

0x3bd359…433a

6 touches
3 conflicts

0xa1087a5c…66c4

0x754704…b603

6 touches
3 conflicts

0x00000000…0000

0xd5b70d…615b

6 touches
3 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: 0x2a68ba18…8e90c5

15 conflicts on slot 0x765c236f2d…b5ff45

← previous block·next block →recent activity