← previous blocknext block →recent activity

Analyzing

Block #73,650,959

38 transactions · 24 stateful · 2026-05-10 09:57:38 UTC

Parallelism

74/100

Blocked

58%

Avg conflicts / tx

1.37

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #73,650,959  ·  38 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0x26452279…b805

0xd32edf…ff58

19 touches
45 conflicts

0xc9e97522…3519

0x2a68ba…90c5

6 touches
3 conflicts

0x00000000…001b

0x1b6862…e19c

6 touches
3 conflicts

0xcb45d9d6…cb83

0x1b6862…e19c

6 touches
3 conflicts

0x17606ba6…1b6e

0x754704…b603

6 touches
3 conflicts

0xa1087a5c…66c4

0x754704…b603

6 touches
3 conflicts

0x00000000…0012

0x1b6862…e19c

4 touches
1 conflict

0x9a555477…19a8

0x754704…b603

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

45 conflicts on slot 0x2645227983…d2b805

← previous block·next block →recent activity