← previous blocknext block →recent activity

Analyzing

Block #73,201,821

21 transactions · 16 stateful · 2026-05-08 08:07:30 UTC

Parallelism

71/100

Blocked

50%

Avg conflicts / tx

0.81

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,201,821  ·  21 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x7f189cf6…afab

0x065c9d…c394

8 touches
6 conflicts

0x22a0450e…fba0

0xd32edf…ff58

7 touches
6 conflicts

0x789a0b6e…2cd2

0x065c9d…c394

6 touches
3 conflicts

0xe09eda07…8dda

0x2a68ba…90c5

6 touches
3 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0xf3808e5a…dbfb

0x34b655…2a6f

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0x0335ae80…8414

0x8d66a4…3095

4 touches
1 conflict

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

6 conflicts on slot 0x7f189cf621…beafab

← previous block·next block →recent activity