← previous blocknext block →recent activity

Analyzing

Block #73,473,911

16 transactions · 14 stateful · 2026-05-09 14:17:45 UTC

Parallelism

81/100

Blocked

29%

Avg conflicts / tx

0.31

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,473,911  ·  16 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

6 touches
3 conflicts

0xc9e97522…3519

0x2a68ba…90c5

4 touches
1 conflict

0x8876d94c…8435

0x2a68ba…90c5

4 touches
1 conflict

0x417f8e94…e9f9

0x065c9d…c394

3 touches
1 conflict

0xa8e1c546…5fb1

0xa6afd3…d132

3 touches
1 conflict

0x00000000…0005

0x0594c7…a3be

2 touches
0 conflicts

0xb02238fc…5e2d

0x0594c7…a3be

2 touches
0 conflicts

0x09000000…0001

0x000000…1000

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

3 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity