← previous blocknext block →recent activity

Analyzing

Block #73,968,497

33 transactions · 25 stateful · 2026-05-11 21:25:32 UTC

Parallelism

79/100

Blocked

48%

Avg conflicts / tx

0.82

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #73,968,497  ·  33 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

0x46f66f86…4af4

0xd32edf…ff58

9 touches
10 conflicts

0xf537eaa0…73c8

0x065c9d…c394

8 touches
6 conflicts

0x9a555477…19a8

0x754704…b603

6 touches
3 conflicts

0xf6cc7de8…0b4a

0x3bd359…433a

6 touches
3 conflicts

0x00000000…0000

0x63e48b…53f2

6 touches
3 conflicts

0x00000000…0003

0x63e48b…53f2

6 touches
3 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0x6f08361d…bda6

0x065c9d…c394

6 touches
3 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 0x46f66f86be…fc4af4

← previous block·next block →recent activity