← previous blocknext block →recent activity

Analyzing

Block #73,964,008

20 transactions · 14 stateful · 2026-05-11 20:55:40 UTC

Parallelism

65/100

Blocked

57%

Avg conflicts / tx

1.15

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #73,964,008  ·  20 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

0x5c347d18…0555

0xd32edf…ff58

13 touches
21 conflicts

0x22e0cc1d…ad04

0x34b655…2a6f

4 touches
1 conflict

0xab2f6eed…254c

0x188d58…ea8e

4 touches
1 conflict

0xab2f6eed…254a

0x188d58…ea8e

4 touches
1 conflict

0x67d47cb1…3fa1

0x188d58…ea8e

2 touches
0 conflicts

0x00000000…0012

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…0013

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…0015

0x1b6862…e19c

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: 0xd32edf66…9fff58

21 conflicts on slot 0x5c347d181f…b90555

← previous block·next block →recent activity