← previous blocknext block →recent activity

Analyzing

Block #73,043,105

42 transactions · 25 stateful · 2026-05-07 14:31:25 UTC

Parallelism

74/100

Blocked

56%

Avg conflicts / tx

1.64

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #73,043,105  ·  42 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

0x6d767a5d…0583

0xd32edf…ff58

21 touches
55 conflicts

0x479ce48c…fa1a

0x1b6862…e19c

10 touches
10 conflicts

0x17606ba6…1b6e

0x754704…b603

10 touches
10 conflicts

0xa1087a5c…66c4

0x754704…b603

10 touches
10 conflicts

0x00000000…0013

0x1b6862…e19c

10 touches
10 conflicts

0x00000000…0015

0x1b6862…e19c

10 touches
10 conflicts

0xc7741b1c…6ec2

0x065c9d…c394

8 touches
6 conflicts

0x92d610a6…9a40

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

55 conflicts on slot 0x6d767a5d2d…d80583

← previous block·next block →recent activity