← previous blocknext block →recent activity

Analyzing

Block #73,273,879

23 transactions · 17 stateful · 2026-05-08 16:06:47 UTC

Parallelism

74/100

Blocked

47%

Avg conflicts / tx

0.74

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,273,879  ·  23 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

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0x0b390c61…dc07

0x065c9d…c394

6 touches
3 conflicts

0xbd7e37a9…9eb5

0x065c9d…c394

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xa1087a5c…66c4

0x754704…b603

6 touches
3 conflicts

0xbdff944d…447e

0x2a68ba…90c5

6 touches
3 conflicts

0x533b21d0…77c2

0xd32edf…ff58

5 touches
3 conflicts

0x3bd55803…5d4c

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: 0x2a68ba18…8e90c5

3 conflicts on slot 0x046a928e85…e50012

← previous block·next block →recent activity