← previous blocknext block →recent activity

Analyzing

Block #73,353,143

19 transactions · 15 stateful · 2026-05-09 00:54:14 UTC

Parallelism

58/100

Blocked

53%

Avg conflicts / tx

1.53

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #73,353,143  ·  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

0x22c6ccda…eac8

0xd32edf…ff58

15 touches
28 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0xd4f655d0…2966

0x065c9d…c394

2 touches
0 conflicts

0x00000000…0012

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…0013

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…0015

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…001d

0x1b6862…e19c

2 touches
0 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

28 conflicts on slot 0x22c6ccda05…39eac8

← previous block·next block →recent activity