← previous blocknext block →recent activity

Analyzing

Block #73,814,643

6 transactions · 6 stateful · 2026-05-11 04:21:00 UTC

Parallelism

67/100

Blocked

17%

Avg conflicts / tx

0.17

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,814,643  ·  6 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0xab910e7d…556a

0x34b655…2a6f

4 touches
1 conflict

0xfa2527aa…9dd5

0x34b655…2a6f

4 touches
1 conflict

0x8240d70c…7c3b

0x34b655…2a6f

4 touches
1 conflict

0x1b5d2e60…99b5

0x34b655…2a6f

2 touches
0 conflicts

0x23114fac…630a

0x34b655…2a6f

2 touches
0 conflicts

0x408e66bb…3d6b

0x34b655…2a6f

2 touches
0 conflicts

0x414e9446…4b59

0x34b655…2a6f

2 touches
0 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

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

1 conflict on slot 0xab910e7d8a…7e556a

← previous block·next block →recent activity