← previous blocknext block →recent activity

Analyzing

Block #73,493,009

11 transactions · 8 stateful · 2026-05-09 16:24:52 UTC

Parallelism

73/100

Blocked

25%

Avg conflicts / tx

0.18

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,493,009  ·  11 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

0x10761540…aec6

0x065c9d…c394

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0xabf379dc…1096

0x065c9d…c394

3 touches
1 conflict

0xb6605ac8…f5ec

0x065c9d…c394

3 touches
1 conflict

0x100cc983…ca76

0x065c9d…c394

2 touches
0 conflicts

0x2f6503c3…b11b

0x065c9d…c394

2 touches
0 conflicts

0x73079886…b705

0x065c9d…c394

2 touches
0 conflicts

0xc2b68712…ac17

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 0x107615406c…65aec6

← previous block·next block →recent activity