← previous blocknext block →recent activity

Analyzing

Block #73,273,546

28 transactions · 20 stateful · 2026-05-08 16:04:34 UTC

Parallelism

82/100

Blocked

45%

Avg conflicts / tx

0.61

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,273,546  ·  28 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x7ba4ebc6…beff

0xd32edf…ff58

9 touches
10 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x47c1a8e8…f74a

0x34b655…2a6f

6 touches
3 conflicts

0xa92c8763…6d7f

0x34b655…2a6f

6 touches
3 conflicts

0xe116a123…0472

0x34b655…2a6f

6 touches
3 conflicts

0xfe3d37ee…6e67

0x34b655…2a6f

6 touches
3 conflicts

0xc5564f8e…f4bf

0xaba216…a862

4 touches
1 conflict

0xd821ae10…fe17

0xc8689a…ee79

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: 0xd32edf66…9fff58

10 conflicts on slot 0x7ba4ebc6f0…5fbeff

← previous block·next block →recent activity