← previous blocknext block →recent activity

Analyzing

Block #73,273,618

37 transactions · 29 stateful · 2026-05-08 16:05:03 UTC

Parallelism

81/100

Blocked

59%

Avg conflicts / tx

1.14

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #73,273,618  ·  37 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x388e001a…7e04

0x34b655…2a6f

12 touches
15 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

10 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…0002

0xab3526…fa38

8 touches
6 conflicts

0x9776ae1b…1a92

0x34b655…2a6f

8 touches
6 conflicts

0xb4b2bfed…9b24

0xd32edf…ff58

7 touches
6 conflicts

0xaa3492db…3703

0x34b655…2a6f

6 touches
3 conflicts

0x038aa895…2f47

0x34b655…2a6f

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

15 conflicts on slot 0x388e001a16…e57e04

← previous block·next block →recent activity