Block #73,473,709

← previous blocknext block →recent activity

Analyzing

Block #73,473,709

6 transactions · 4 stateful · 2026-05-09 14:16:24 UTC

Parallelism

50/100

Blocked

50%

Avg conflicts / tx

0.5

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,473,709  ·  6 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

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xa15427f6…d932

0x34b655…2a6f

6 touches
3 conflicts

0x070a562a…8147

0x34b655…2a6f

4 touches
1 conflict

0x0eac6378…36f4

0x34b655…2a6f

4 touches
1 conflict

0xe9c3898e…2684

0x34b655…2a6f

4 touches
1 conflict

0x05638a8b…d586

0x34b655…2a6f

4 touches
1 conflict

0x71ed9e8f…24ea

0x34b655…2a6f

2 touches
0 conflicts

0x7cee1be1…e770

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

3 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity