← previous blocknext block →recent activity

Analyzing

Block #73,917,552

6 transactions · 5 stateful · 2026-05-11 15:46:38 UTC

Parallelism

67/100

Blocked

20%

Avg conflicts / tx

0.17

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,917,552  ·  6 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

0xf537eaa0…73c8

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x0cbd20da…74d2

0x065c9d…c394

2 touches
0 conflicts

0x1f812c3b…72b0

0x065c9d…c394

2 touches
0 conflicts

0x2b59e24e…9c62

0x065c9d…c394

2 touches
0 conflicts

0x2c4780c3…6d46

0x065c9d…c394

2 touches
0 conflicts

0x4f47c431…b8b7

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 0xf537eaa0c6…3873c8

← previous block·next block →recent activity