← previous blocknext block →recent activity

Analyzing

Block #73,598,703

30 transactions · 23 stateful · 2026-05-10 04:07:19 UTC

Parallelism

60/100

Blocked

61%

Avg conflicts / tx

2.17

Longest chain

12 deep

Execution timeline

did this block parallelize well?

view

block #73,598,703  ·  30 txs across 12 waves  ·  depth 12
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

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

0x5572c205…200a

0xd32edf…ff58

21 touches
55 conflicts

0xba5743c7…21c1

0x1b6862…e19c

10 touches
10 conflicts

0x01e7b865…6e6d

0x188d58…ea8e

10 touches
10 conflicts

0x01e7b865…6e6e

0x188d58…ea8e

10 touches
10 conflicts

0x00000000…0013

0x1b6862…e19c

10 touches
10 conflicts

0x00000000…0015

0x1b6862…e19c

10 touches
10 conflicts

0x17606ba6…1b6e

0x754704…b603

10 touches
10 conflicts

0x00000000…002a

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 0x5572c205bd…45200a

← previous block·next block →recent activity