Block #73,042,054

← previous blocknext block →recent activity

Analyzing

Block #73,042,054

30 transactions · 27 stateful · 2026-05-07 14:24:24 UTC

Parallelism

60/100

Blocked

59%

Avg conflicts / tx

1.87

Longest chain

12 deep

Execution timeline

did this block parallelize well?

view

block #73,042,054  ·  30 txs across 12 waves  ·  depth 12
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

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

0xd98b3c10…67b8

0x34b655…2a6f

14 touches
21 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

12 touches
15 conflicts

0x388e001a…7e04

0x34b655…2a6f

10 touches
10 conflicts

0xc824469a…6425

0x34b655…2a6f

10 touches
10 conflicts

0x00000000…0002

0xab3526…fa38

8 touches
6 conflicts

0xb77c59ad…4c74

0x34b655…2a6f

8 touches
6 conflicts

0x8a35acfb…d1aa

0x8d66a4…3095

8 touches
6 conflicts

0xba33378a…f1df

0x34b655…2a6f

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

21 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity