← previous blocknext block →recent activity

Analyzing

Block #73,651,721

19 transactions · 11 stateful · 2026-05-10 10:02:43 UTC

Parallelism

89/100

Blocked

27%

Avg conflicts / tx

0.16

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,651,721  ·  19 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x5618dbe3…ca7b

0x34b655…2a6f

4 touches
1 conflict

0xf2438038…5fa7

0x34b655…2a6f

4 touches
1 conflict

0x17606ba6…1b6e

0x754704…b603

4 touches
1 conflict

0x2ddde657…3bca

0xd32edf…ff58

3 touches
1 conflict

0x1c774ab3…59be

0x065c9d…c394

2 touches
0 conflicts

0x326e4962…dadc

0x065c9d…c394

2 touches
0 conflicts

0x70101a3b…d440

0x065c9d…c394

2 touches
0 conflicts

0xdf361ded…14cd

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

1 conflict on slot 0x5618dbe3e5…25ca7b

← previous block·next block →recent activity