Block #73,338,081

← previous blocknext block →recent activity

Analyzing

Block #73,338,081

30 transactions · 23 stateful · 2026-05-08 23:13:57 UTC

Parallelism

70/100

Blocked

70%

Avg conflicts / tx

2

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #73,338,081  ·  30 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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…0002

0xab3526…fa38

18 touches
36 conflicts

0x318ac0bb…6b9c

0x34b655…2a6f

14 touches
21 conflicts

0x2484cc15…5afc

0x34b655…2a6f

6 touches
3 conflicts

0xafd59af5…5257

0xc8689a…ee79

6 touches
3 conflicts

0x15c9b5bf…f732

0x34b655…2a6f

6 touches
3 conflicts

0xa2fe477b…8933

0x34b655…2a6f

6 touches
3 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

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: 0xab35264b…1cfa38

36 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity