← previous blocknext block →recent activity

Analyzing

Block #73,600,355

18 transactions · 14 stateful · 2026-05-10 04:18:21 UTC

Parallelism

83/100

Blocked

29%

Avg conflicts / tx

0.28

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,600,355  ·  18 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

0x68cc2e0f…bffb

0xd32edf…ff58

5 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x0d0b2509…074d

0x3bd359…433a

4 touches
1 conflict

0xe6455d1f…1029

0x754704…b603

4 touches
1 conflict

0x22e295f5…1bef

0x065c9d…c394

2 touches
0 conflicts

0x41521e95…0475

0x065c9d…c394

2 touches
0 conflicts

0x4d87512b…897c

0x065c9d…c394

2 touches
0 conflicts

0x6f08361d…bda6

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 0x68cc2e0f52…3ebffb

← previous block·next block →recent activity