← previous blocknext block →recent activity

Analyzing

Block #73,523,388

20 transactions · 17 stateful · 2026-05-09 19:46:57 UTC

Parallelism

65/100

Blocked

65%

Avg conflicts / tx

1.45

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #73,523,388  ·  20 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

0x6452c729…fec6

0xd32edf…ff58

13 touches
21 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

8 touches
6 conflicts

0xae69c125…2379

0x2a68ba…90c5

4 touches
1 conflict

0x0d0b2509…074d

0x3bd359…433a

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0xe6455d1f…1029

0x754704…b603

4 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…0019

0x1b6862…e19c

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: 0xd32edf66…9fff58

21 conflicts on slot 0x6452c7290c…32fec6

← previous block·next block →recent activity