← previous blocknext block →recent activity

Analyzing

Block #73,571,710

17 transactions · 13 stateful · 2026-05-10 01:07:50 UTC

Parallelism

76/100

Blocked

31%

Avg conflicts / tx

0.29

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,571,710  ·  17 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

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x22e295f5…1bef

0x065c9d…c394

4 touches
1 conflict

0x1a4b4152…0a08

0x6c4bfa…a540

4 touches
1 conflict

0x00000000…0002

0xab3526…fa38

4 touches
1 conflict

0xed57bddf…1abf

0xc8689a…ee79

4 touches
1 conflict

0xefa46e73…dff5

0x065c9d…c394

3 touches
1 conflict

0xb7ecde59…5e99

0xd32edf…ff58

3 touches
1 conflict

0x09000000…0001

0x000000…1000

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

3 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity