← previous blocknext block →recent activity

Analyzing

Block #73,041,897

20 transactions · 15 stateful · 2026-05-07 14:23:21 UTC

Parallelism

75/100

Blocked

33%

Avg conflicts / tx

0.55

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,041,897  ·  20 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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…0002

0xd574ca…7ab1

10 touches
10 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0x9cc607d0…c9c7

0x34b655…2a6f

4 touches
1 conflict

0x6eba5e7f…4b52

0x34b655…2a6f

4 touches
1 conflict

0x20ac0567…c954

0x34b655…2a6f

2 touches
0 conflicts

0x220f4f84…15f8

0x34b655…2a6f

2 touches
0 conflicts

0x313f2565…5b00

0x34b655…2a6f

2 touches
0 conflicts

0x32ee90db…decc

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: 0xd574cae5…037ab1

10 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity