Block #73,333,824

← previous blocknext block →recent activity

Analyzing

Block #73,333,824

12 transactions · 9 stateful · 2026-05-08 22:45:39 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,333,824  ·  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

0x4a3e7480…2405

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x7b5187b1…5285

0x065c9d…c394

3 touches
1 conflict

0x1af59a5f…86ba

0x065c9d…c394

3 touches
1 conflict

0x6f08361d…bda6

0x065c9d…c394

2 touches
0 conflicts

0xb556f457…7cd8

0x065c9d…c394

2 touches
0 conflicts

0xbb9ca88c…bf57

0x065c9d…c394

2 touches
0 conflicts

0xf537eaa0…73c8

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 0x4a3e7480c3…232405

← previous block·next block →recent activity