← previous blocknext block →recent activity

Analyzing

Block #73,490,247

18 transactions · 15 stateful · 2026-05-09 16:06:35 UTC

Parallelism

50/100

Blocked

60%

Avg conflicts / tx

1.44

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #73,490,247  ·  18 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

0x6bf62caf…587f

0xd32edf…ff58

11 touches
15 conflicts

0x046a928e…0012

0x2a68ba…90c5

10 touches
10 conflicts

0xa1087a5c…66c4

0x754704…b603

6 touches
3 conflicts

0xc9e97522…3519

0x2a68ba…90c5

6 touches
3 conflicts

0x083a8763…5a78

0x1b6862…e19c

4 touches
1 conflict

0x592e8cb3…24f0

0x065c9d…c394

4 touches
1 conflict

0x00000000…0013

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

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

15 conflicts on slot 0x6bf62cafd6…ba587f

← previous block·next block →recent activity