← previous blocknext block →recent activity

Analyzing

Block #73,211,944

6 transactions · 6 stateful · 2026-05-08 09:14:47 UTC

Parallelism

50/100

Blocked

33%

Avg conflicts / tx

0.5

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,211,944  ·  6 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

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x7f189cf6…afab

0x065c9d…c394

4 touches
1 conflict

0x00000000…000b

0x6ca43f…c331

4 touches
1 conflict

0x5b031a6e…fd42

0x065c9d…c394

4 touches
1 conflict

0x554f1ada…6916

0x6ca43f…c331

4 touches
1 conflict

0x4e5ebbf7…ae70

0xc8689a…ee79

4 touches
1 conflict

0x01d486f7…7499

0x065c9d…c394

2 touches
1 conflict

0x01d486f7…7498

0x065c9d…c394

2 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

3 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity