← previous blocknext block →recent activity

Analyzing

Block #73,261,057

26 transactions · 22 stateful · 2026-05-08 14:41:23 UTC

Parallelism

77/100

Blocked

45%

Avg conflicts / tx

1.08

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,261,057  ·  26 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x00000000…003d

0x065c9d…c394

12 touches
15 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0x737acb78…fce8

0x34b655…2a6f

6 touches
3 conflicts

0x87a380d9…2d04

0x34b655…2a6f

6 touches
3 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0xeeb38aa7…8f00

0x34b655…2a6f

6 touches
3 conflicts

0xf8f1e808…a4fd

0x34b655…2a6f

6 touches
3 conflicts

0x046a928e…0012

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: 0x065c9d28…a9c394

15 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity