Block #73,493,203

← previous blocknext block →recent activity

Analyzing

Block #73,493,203

23 transactions · 18 stateful · 2026-05-09 16:26:10 UTC

Parallelism

65/100

Blocked

56%

Avg conflicts / tx

1.13

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #73,493,203  ·  23 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

8 touches
6 conflicts

0x22e295f5…1bef

0x065c9d…c394

8 touches
6 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0x689cd5fd…5556

0x34b655…2a6f

4 touches
1 conflict

0x7b50a82b…f53d

0x34b655…2a6f

4 touches
1 conflict

0x83cde744…b76b

0x34b655…2a6f

4 touches
1 conflict

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: 0x34b6552d…112a6f

10 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity