← previous blocknext block →recent activity

Analyzing

Block #73,336,175

36 transactions · 29 stateful · 2026-05-08 23:01:14 UTC

Parallelism

64/100

Blocked

66%

Avg conflicts / tx

2.56

Longest chain

13 deep

Execution timeline

did this block parallelize well?

view

block #73,336,175  ·  36 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

0xa56c70c6…a05f

0xd32edf…ff58

21 touches
55 conflicts

0xf537eaa0…73c8

0x065c9d…c394

16 touches
28 conflicts

0x00000000…003d

0x065c9d…c394

12 touches
15 conflicts

0x046a928e…0012

0x2a68ba…90c5

12 touches
15 conflicts

0x00000000…0013

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0015

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…001d

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…002d

0x1b6862…e19c

8 touches
6 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

55 conflicts on slot 0xa56c70c6a4…8ea05f

← previous block·next block →recent activity