← previous blocknext block →recent activity

Analyzing

Block #73,681,642

47 transactions · 31 stateful · 2026-05-10 13:24:44 UTC

Parallelism

72/100

Blocked

71%

Avg conflicts / tx

1.87

Longest chain

13 deep

Execution timeline

did this block parallelize well?

view

block #73,681,642  ·  47 txs across 13 waves  ·  depth 13
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

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

0x22426edc…d8ff

0xd32edf…ff58

21 touches
55 conflicts

0x00000000…003d

0x065c9d…c394

12 touches
15 conflicts

0x529acb6a…fcc6

0x065c9d…c394

12 touches
15 conflicts

0x17606ba6…1b6e

0x754704…b603

12 touches
15 conflicts

0x01e7b865…6e6d

0x188d58…ea8e

10 touches
10 conflicts

0x00000000…0013

0x1b6862…e19c

10 touches
10 conflicts

0x00000000…0015

0x1b6862…e19c

10 touches
10 conflicts

0xab2a87f1…eaff

0x1b6862…e19c

10 touches
10 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

55 conflicts on slot 0x22426edc15…49d8ff

← previous block·next block →recent activity