Block #73,338,274

← previous blocknext block →recent activity

Analyzing

Block #73,338,274

40 transactions · 26 stateful · 2026-05-08 23:15:14 UTC

Parallelism

68/100

Blocked

69%

Avg conflicts / tx

2.17

Longest chain

13 deep

Execution timeline

did this block parallelize well?

view

block #73,338,274  ·  40 txs across 13 waves  ·  depth 13
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

wave w12

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

0xac6ee683…30c8

0xd32edf…ff58

23 touches
66 conflicts

0x17606ba6…1b6e

0x754704…b603

10 touches
10 conflicts

0x846f2172…fd54

0x0555e3…2b9c

6 touches
3 conflicts

0x09beabbc…065c

0x188d58…ea8e

6 touches
3 conflicts

0x12309510…0ac2

0x000000…012a

6 touches
3 conflicts

0x18aed20c…48f3

0x000000…012a

6 touches
3 conflicts

0xe75ce681…ba5f

0x188d58…ea8e

6 touches
3 conflicts

0xe75ce681…ba61

0x188d58…ea8e

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: 0xd32edf66…9fff58

66 conflicts on slot 0xac6ee68344…cb30c8

← previous block·next block →recent activity