← previous blocknext block →recent activity

Analyzing

Block #73,639,255

14 transactions · 10 stateful · 2026-05-10 08:38:51 UTC

Parallelism

71/100

Blocked

40%

Avg conflicts / tx

0.5

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,639,255  ·  14 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

6 touches
3 conflicts

0xbb99f035…a59c

0x065c9d…c394

5 touches
3 conflicts

0x4813a6f6…1bc4

0xd32edf…ff58

5 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x4d87512b…897c

0x065c9d…c394

4 touches
1 conflict

0x22e295f5…1bef

0x065c9d…c394

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0x45064d6b…bce9

0x754704…b603

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

3 conflicts on slot 0xc9e9752290…9c3519

← previous block·next block →recent activity