Block #73,204,615

← previous blocknext block →recent activity

Analyzing

Block #73,204,615

8 transactions · 8 stateful · 2026-05-08 08:26:03 UTC

Parallelism

75/100

Blocked

13%

Avg conflicts / tx

0.13

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,204,615  ·  8 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

0x1b5d2e60…99b5

0x34b655…2a6f

4 touches
1 conflict

0x21d22421…0b7a

0x34b655…2a6f

4 touches
1 conflict

0xb8c01ecf…9aa9

0x34b655…2a6f

4 touches
1 conflict

0xea02471d…1542

0x34b655…2a6f

4 touches
1 conflict

0xf4730a2d…3538

0x34b655…2a6f

4 touches
1 conflict

0x4f29a567…ee4f

0x065c9d…c394

2 touches
0 conflicts

0x7f189cf6…afab

0x065c9d…c394

2 touches
0 conflicts

0xbd2fca5c…7157

0x065c9d…c394

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 0x1b5d2e607a…9999b5

← previous block·next block →recent activity