← previous blocknext block →recent activity

Analyzing

Block #73,343,734

19 transactions · 16 stateful · 2026-05-08 23:51:32 UTC

Parallelism

68/100

Blocked

38%

Avg conflicts / tx

0.63

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,343,734  ·  19 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

0x88dcc402…6361

0xd32edf…ff58

9 touches
10 conflicts

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0x8cd7a217…48a6

0x065c9d…c394

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0x00000000…0002

0xab3526…fa38

4 touches
1 conflict

0x35801c67…bcc3

0x1b6862…e19c

2 touches
0 conflicts

0x12530975…a089

0x3bd359…433a

2 touches
0 conflicts

0x4bef88e0…eaca

0x3bd359…433a

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

10 conflicts on slot 0x88dcc40225…896361

← previous block·next block →recent activity