← previous blocknext block →recent activity

Analyzing

Block #73,975,073

11 transactions · 9 stateful · 2026-05-11 22:09:37 UTC

Parallelism

73/100

Blocked

22%

Avg conflicts / tx

0.27

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,975,073  ·  11 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x23951077…539b

0x34b655…2a6f

4 touches
1 conflict

0xf853eb8e…4027

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xee230b20…5a0f

0x34b655…2a6f

4 touches
1 conflict

0x1b9e654e…0a08

0x34b655…2a6f

2 touches
0 conflicts

0x9d92359d…0ca7

0x34b655…2a6f

2 touches
0 conflicts

0xbbe5c289…487d

0x34b655…2a6f

2 touches
0 conflicts

0xd3844ce0…349a

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 0x2395107727…b6539b

← previous block·next block →recent activity