Block #73,261,293

← previous blocknext block →recent activity

Analyzing

Block #73,261,293

19 transactions · 17 stateful · 2026-05-08 14:42:57 UTC

Parallelism

58/100

Blocked

65%

Avg conflicts / tx

1.84

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #73,261,293  ·  19 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

16 touches
28 conflicts

0x79536e13…bfc1

0x34b655…2a6f

6 touches
3 conflicts

0x6cab9ef4…f849

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x4194823b…c8d0

0x34b655…2a6f

4 touches
1 conflict

0xe4af4c87…9964

0x34b655…2a6f

4 touches
1 conflict

0x81e1f4e8…08d7

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

28 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity