Block #73,374,962

← previous blocknext block →recent activity

Analyzing

Block #73,374,962

28 transactions · 26 stateful · 2026-05-09 03:19:17 UTC

Parallelism

53/100

Blocked

58%

Avg conflicts / tx

2.04

Longest chain

13 deep

Execution timeline

did this block parallelize well?

view

block #73,374,962  ·  28 txs across 13 waves  ·  depth 13
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

wave w12

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

0xc3c8642a…7da5

0x2a68ba…90c5

16 touches
28 conflicts

0x9ce0774c…ed1a

0xd32edf…ff58

15 touches
28 conflicts

0xbeccfac5…a45e

0x065c9d…c394

13 touches
21 conflicts

0xa1087a5c…66c4

0x754704…b603

12 touches
15 conflicts

0xf6cc7de8…0b4a

0x3bd359…433a

10 touches
10 conflicts

0x00000000…0000

0x63e48b…53f2

10 touches
10 conflicts

0x9a555477…19a8

0x754704…b603

10 touches
10 conflicts

0x00000000…0004

0x63e48b…53f2

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

28 conflicts on slot 0xc3c8642ae9…317da5

← previous block·next block →recent activity