← previous blocknext block →recent activity

Analyzing

Block #73,493,044

20 transactions · 16 stateful · 2026-05-09 16:25:06 UTC

Parallelism

50/100

Blocked

63%

Avg conflicts / tx

2.3

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #73,493,044  ·  20 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

0x72dd650c…1429

0xd32edf…ff58

19 touches
45 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0028

0x1b6862…e19c

4 touches
1 conflict

0x872e51c8…ae25

0x1b6862…e19c

4 touches
1 conflict

0xf6cc7de8…0b4a

0x3bd359…433a

4 touches
1 conflict

0x00000000…0000

0x63e48b…53f2

4 touches
1 conflict

0x00000000…0003

0x63e48b…53f2

4 touches
1 conflict

0x00000000…0004

0x63e48b…53f2

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

45 conflicts on slot 0x72dd650c5b…621429

← previous block·next block →recent activity