← previous blocknext block →recent activity

Analyzing

Block #73,214,559

22 transactions · 16 stateful · 2026-05-08 09:32:07 UTC

Parallelism

55/100

Blocked

56%

Avg conflicts / tx

2.05

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #73,214,559  ·  22 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0x223b7359…fab9

0xd32edf…ff58

19 touches
45 conflicts

0x09000000…0007

0x000000…1000

2 touches
0 conflicts

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x0b390c61…dc07

0x065c9d…c394

2 touches
0 conflicts

0x20aa7eb3…552c

0x065c9d…c394

2 touches
0 conflicts

0x00000000…0012

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…0013

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…0015

0x1b6862…e19c

2 touches
0 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 0x223b7359f7…81fab9

← previous block·next block →recent activity