← previous blocknext block →recent activity

Analyzing

Block #73,663,859

12 transactions · 9 stateful · 2026-05-10 11:24:33 UTC

Parallelism

83/100

Blocked

11%

Avg conflicts / tx

0.08

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,663,859  ·  12 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

0xc9e97522…3519

0x2a68ba…90c5

4 touches
1 conflict

0x6cb247c7…83cd

0x065c9d…c394

3 touches
1 conflict

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x05706d6d…8b3c

0x065c9d…c394

2 touches
0 conflicts

0x11d2c5f3…adb4

0x065c9d…c394

2 touches
0 conflicts

0x27a4f763…b20c

0x065c9d…c394

2 touches
0 conflicts

0x50c9e2a0…7cf8

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: 0x2a68ba18…8e90c5

1 conflict on slot 0xc9e9752290…9c3519

← previous block·next block →recent activity