← previous blocknext block →recent activity

Analyzing

Block #73,660,380

31 transactions · 25 stateful · 2026-05-10 11:01:04 UTC

Parallelism

81/100

Blocked

48%

Avg conflicts / tx

0.77

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,660,380  ·  31 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x38524fae…9deb

0x34b655…2a6f

10 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x5e3c21d1…6e30

0xd32edf…ff58

7 touches
6 conflicts

0xac206e47…ef7d

0x34b655…2a6f

6 touches
3 conflicts

0x4546ebad…b908

0x34b655…2a6f

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

4 touches
1 conflict

0x1c5f861c…787f

0x34b655…2a6f

4 touches
1 conflict

0x6af306bb…2e81

0x3bd359…433a

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 0x38524faed4…ae9deb

← previous block·next block →recent activity