← previous blocknext block →recent activity

Analyzing

Block #73,046,268

20 transactions · 14 stateful · 2026-05-07 14:52:30 UTC

Parallelism

90/100

Blocked

21%

Avg conflicts / tx

0.15

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,046,268  ·  20 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

0x70b2f813…783c

0x2a68ba…90c5

4 touches
1 conflict

0x00000000…0002

0xab3526…fa38

4 touches
1 conflict

0x238e2dca…0cdc

0x065c9d…c394

3 touches
1 conflict

0xb1ff0f5c…33fd

0xd32edf…ff58

3 touches
1 conflict

0x04dc4440…5cb0

0x065c9d…c394

2 touches
0 conflicts

0x0e36092b…e6eb

0x065c9d…c394

2 touches
0 conflicts

0x3c301108…cc61

0x065c9d…c394

2 touches
0 conflicts

0x4e9ef689…dc1d

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: 0x2a68ba18…8e90c5

1 conflict on slot 0x70b2f81398…04783c

← previous block·next block →recent activity