← previous blocknext block →recent activity

Analyzing

Block #73,693,453

30 transactions · 22 stateful · 2026-05-10 14:44:19 UTC

Parallelism

73/100

Blocked

41%

Avg conflicts / tx

1.1

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #73,693,453  ·  30 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

0x2e24858e…7035

0xd32edf…ff58

15 touches
28 conflicts

0xcb45d9d6…cb84

0x1b6862…e19c

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0012

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…001c

0x1b6862…e19c

6 touches
3 conflicts

0x85a88798…f85e

0x34b655…2a6f

4 touches
1 conflict

0x8aa1941d…2988

0x34b655…2a6f

4 touches
1 conflict

0x9dfb215c…3c58

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: 0xd32edf66…9fff58

28 conflicts on slot 0x2e24858efe…b77035

← previous block·next block →recent activity