← previous blocknext block →recent activity

Analyzing

Block #73,490,241

27 transactions · 23 stateful · 2026-05-09 16:06:32 UTC

Parallelism

44/100

Blocked

83%

Avg conflicts / tx

2.81

Longest chain

15 deep

Execution timeline

did this block parallelize well?

view

block #73,490,241  ·  27 txs across 15 waves  ·  depth 15
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

wave w13

wave w14

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

0xc3ba6871…ae8a

0xd32edf…ff58

19 touches
45 conflicts

0x046a928e…0012

0x2a68ba…90c5

12 touches
15 conflicts

0x00000000…003d

0x065c9d…c394

10 touches
10 conflicts

0x22e295f5…1bef

0x065c9d…c394

10 touches
10 conflicts

0x00000000…0015

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0018

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0028

0x1b6862…e19c

8 touches
6 conflicts

0xba5743c7…21bf

0x1b6862…e19c

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

45 conflicts on slot 0xc3ba68713a…faae8a

← previous block·next block →recent activity