Block #73,170,903

← previous blocknext block →recent activity

Analyzing

Block #73,170,903

16 transactions · 15 stateful · 2026-05-08 04:41:26 UTC

Parallelism

63/100

Blocked

47%

Avg conflicts / tx

1.25

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,170,903  ·  16 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

0x62180eb6…5f53

0xd32edf…ff58

11 touches
15 conflicts

0x6af306bb…2e81

0x3bd359…433a

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0xba5743c7…21c1

0x1b6862…e19c

6 touches
3 conflicts

0xce8bbe33…b72e

0x3bd359…433a

6 touches
3 conflicts

0xf91b744e…9117

0x754704…b603

6 touches
3 conflicts

0x00000000…001a

0x1b6862…e19c

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

15 conflicts on slot 0x62180eb627…be5f53

← previous block·next block →recent activity