← previous blocknext block →recent activity

Analyzing

Block #73,377,024

19 transactions · 16 stateful · 2026-05-09 03:32:59 UTC

Parallelism

47/100

Blocked

63%

Avg conflicts / tx

2.11

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #73,377,024  ·  19 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0xf3cea90e…556c

0xd32edf…ff58

15 touches
28 conflicts

0xc3c8642a…7da5

0x2a68ba…90c5

10 touches
10 conflicts

0xa1087a5c…66c4

0x754704…b603

10 touches
10 conflicts

0x49a46488…2bf6

0x065c9d…c394

7 touches
6 conflicts

0xf58eca50…59fc

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x4d87512b…897c

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

28 conflicts on slot 0xf3cea90e96…27556c

← previous block·next block →recent activity