Block #73,211,214

← previous blocknext block →recent activity

Analyzing

Block #73,211,214

13 transactions · 10 stateful · 2026-05-08 09:09:56 UTC

Parallelism

77/100

Blocked

30%

Avg conflicts / tx

0.23

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,211,214  ·  13 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

0xe1de9b4d…39a2

0x065c9d…c394

4 touches
1 conflict

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0x00000000…0002

0xab3526…fa38

4 touches
1 conflict

0x3d56ba1b…9a1f

0x065c9d…c394

3 touches
1 conflict

0x38020512…8bb6

0x065c9d…c394

3 touches
1 conflict

0xb1a2a12b…3028

0x065c9d…c394

2 touches
0 conflicts

0xb4865d7b…eb3e

0x065c9d…c394

2 touches
0 conflicts

0xcbbc6842…c806

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: 0x065c9d28…a9c394

1 conflict on slot 0xe1de9b4da2…f939a2

← previous block·next block →recent activity