← previous blocknext block →recent activity

Analyzing

Block #73,336,204

29 transactions · 19 stateful · 2026-05-08 23:01:25 UTC

Parallelism

76/100

Blocked

53%

Avg conflicts / tx

1.03

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #73,336,204  ·  29 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

0x968ff3c8…63d3

0xd32edf…ff58

13 touches
21 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0xf537eaa0…73c8

0x065c9d…c394

4 touches
1 conflict

0x8d0dfe2c…3345

0x2a68ba…90c5

4 touches
1 conflict

0x729a7747…9c1e

0x065c9d…c394

3 touches
1 conflict

0x798bc6d5…aa24

0x065c9d…c394

3 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

21 conflicts on slot 0x968ff3c8a6…7463d3

← previous block·next block →recent activity