← previous blocknext block →recent activity

Analyzing

Block #73,016,307

20 transactions · 17 stateful · 2026-05-07 11:33:00 UTC

Parallelism

70/100

Blocked

41%

Avg conflicts / tx

0.95

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,016,307  ·  20 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

0x00000000…003d

0x065c9d…c394

10 touches
10 conflicts

0x046a928e…0012

0x2a68ba…90c5

8 touches
6 conflicts

0xbd7e37a9…9eb5

0x065c9d…c394

8 touches
6 conflicts

0x0b390c61…dc07

0x065c9d…c394

8 touches
6 conflicts

0x9b1a47c3…69f8

0xde22b2…7777

4 touches
1 conflict

0x503ee695…ff73

0x065c9d…c394

4 touches
1 conflict

0xbf25e763…684f

0x3bd359…433a

4 touches
1 conflict

0x00000000…0000

0x776059…1d8d

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: 0x065c9d28…a9c394

10 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity