Block #73,333,839

← previous blocknext block →recent activity

Analyzing

Block #73,333,839

11 transactions · 9 stateful · 2026-05-08 22:45:45 UTC

Parallelism

82/100

Blocked

11%

Avg conflicts / tx

0.18

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,333,839  ·  11 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

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x0d9436be…8f04

0x065c9d…c394

2 touches
0 conflicts

0x47185b3a…8f4f

0x065c9d…c394

2 touches
0 conflicts

0x4a3e7480…2405

0x065c9d…c394

2 touches
0 conflicts

0x8af7be83…3992

0x065c9d…c394

2 touches
0 conflicts

0xcbc38ffb…2e6a

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 0x0000000000…00003d

← previous block·next block →recent activity