← previous blocknext block →recent activity

Analyzing

Block #73,483,970

16 transactions · 14 stateful · 2026-05-09 15:24:39 UTC

Parallelism

81/100

Blocked

21%

Avg conflicts / tx

0.25

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,483,970  ·  16 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

0xb389d45f…8a4c

0x34b655…2a6f

6 touches
3 conflicts

0x17606ba6…1b6e

0x754704…b603

4 touches
1 conflict

0x266483fe…b227

0x34b655…2a6f

4 touches
1 conflict

0x403295dc…8fb0

0x34b655…2a6f

4 touches
1 conflict

0x66149d3e…b214

0x34b655…2a6f

4 touches
1 conflict

0x97b0b2ee…4666

0x34b655…2a6f

4 touches
1 conflict

0xa3ff1ab2…8ae3

0x34b655…2a6f

4 touches
1 conflict

0xa92c8763…6d7f

0x34b655…2a6f

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: 0x34b6552d…112a6f

3 conflicts on slot 0xb389d45f2b…a98a4c

← previous block·next block →recent activity