← previous blocknext block →recent activity

Analyzing

Block #73,657,795

37 transactions · 27 stateful · 2026-05-10 10:43:44 UTC

Parallelism

60/100

Blocked

74%

Avg conflicts / tx

3.16

Longest chain

15 deep

Execution timeline

did this block parallelize well?

view

block #73,657,795  ·  37 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

0x19c82926…4d40

0xd32edf…ff58

29 touches
105 conflicts

0x00000000…001c

0x1b6862…e19c

12 touches
15 conflicts

0xcb45d9d6…cb84

0x1b6862…e19c

12 touches
15 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

10 touches
10 conflicts

0x00000000…0012

0x1b6862…e19c

10 touches
10 conflicts

0xb159af88…a9e7

0x065c9d…c394

8 touches
6 conflicts

0xa1087a5c…66c4

0x754704…b603

8 touches
6 conflicts

0xae69c125…2379

0x2a68ba…90c5

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

105 conflicts on slot 0x19c82926ba…c54d40

← previous block·next block →recent activity