Block #73,324,415

← previous blocknext block →recent activity

Analyzing

Block #73,324,415

7 transactions · 7 stateful · 2026-05-08 21:43:06 UTC

Parallelism

71/100

Blocked

14%

Avg conflicts / tx

0.14

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,324,415  ·  7 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

0x0b390c61…dc07

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xfd0bab67…1154

0x065c9d…c394

3 touches
1 conflict

0x282e8272…764e

0x065c9d…c394

2 touches
0 conflicts

0x2ff1dff2…d345

0x065c9d…c394

2 touches
0 conflicts

0x6a41b781…a0a7

0x065c9d…c394

2 touches
0 conflicts

0x86c8877b…d086

0x065c9d…c394

2 touches
0 conflicts

0x884d6d79…1a81

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: 0x065c9d28…a9c394

1 conflict on slot 0x0b390c6160…02dc07

← previous block·next block →recent activity