← previous blocknext block →recent activity

Analyzing

Block #73,034,207

36 transactions · 32 stateful · 2026-05-07 13:32:13 UTC

Parallelism

69/100

Blocked

66%

Avg conflicts / tx

2.17

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #73,034,207  ·  36 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

0xd98b3c10…67b8

0x34b655…2a6f

18 touches
36 conflicts

0x388e001a…7e04

0x34b655…2a6f

12 touches
15 conflicts

0x00000000…0015

0x1b6862…e19c

10 touches
10 conflicts

0x00000000…001f

0x1b6862…e19c

10 touches
10 conflicts

0x00000000…002f

0x1b6862…e19c

10 touches
10 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

10 touches
10 conflicts

0xda6b535e…6d6e

0x1b6862…e19c

10 touches
10 conflicts

0x00000000…0002

0xd574ca…7ab1

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: 0x34b6552d…112a6f

36 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity