← previous blocknext block →recent activity

Analyzing

Block #73,393,439

28 transactions · 23 stateful · 2026-05-09 05:22:12 UTC

Parallelism

53/100

Blocked

61%

Avg conflicts / tx

1.96

Longest chain

13 deep

Execution timeline

did this block parallelize well?

view

block #73,393,439  ·  28 txs across 13 waves  ·  depth 13
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

wave w12

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

0x408453cb…00df

0xd32edf…ff58

17 touches
36 conflicts

0x00000000…003d

0x065c9d…c394

12 touches
15 conflicts

0x4d87512b…897c

0x065c9d…c394

10 touches
10 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

4 touches
1 conflict

0x22e295f5…1bef

0x065c9d…c394

4 touches
1 conflict

0x00000000…001e

0x1b6862…e19c

4 touches
1 conflict

0x00000000…002e

0x1b6862…e19c

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

36 conflicts on slot 0x408453cb1f…b600df

← previous block·next block →recent activity