← previous blocknext block →recent activity

Analyzing

Block #73,611,180

9 transactions · 7 stateful · 2026-05-10 05:30:18 UTC

Parallelism

67/100

Blocked

29%

Avg conflicts / tx

0.33

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,611,180  ·  9 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

0xca88c1b9…76dd

0xd32edf…ff58

5 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x98067f20…59e6

0x1b6862…e19c

4 touches
1 conflict

0x04e6849c…b447

0x065c9d…c394

2 touches
0 conflicts

0x1f3f3d77…e2e1

0x065c9d…c394

2 touches
0 conflicts

0x6c491103…48e8

0x065c9d…c394

2 touches
0 conflicts

0x8a9b6b3e…f653

0x065c9d…c394

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

3 conflicts on slot 0xca88c1b9de…e476dd

← previous block·next block →recent activity