← previous blocknext block →recent activity

Analyzing

Block #73,661,298

37 transactions · 25 stateful · 2026-05-10 11:07:15 UTC

Parallelism

76/100

Blocked

56%

Avg conflicts / tx

1.27

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #73,661,298  ·  37 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

0x2b418fb1…7631

0xd32edf…ff58

17 touches
36 conflicts

0x17606ba6…1b6e

0x754704…b603

8 touches
6 conflicts

0x6af306bb…2e81

0x3bd359…433a

6 touches
3 conflicts

0xcb45d9d6…cb84

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0012

0x1b6862…e19c

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

0xf91b744e…9117

0x754704…b603

6 touches
3 conflicts

0xc9e97522…3519

0x2a68ba…90c5

6 touches
3 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

36 conflicts on slot 0x2b418fb1c9…687631

← previous block·next block →recent activity