Block #72,394,835

← previous blocknext block →recent activity

Analyzing

Block #72,394,835

11 transactions · 9 stateful · 2026-05-04 14:32:47 UTC

Parallelism

82/100

Blocked

11%

Avg conflicts / tx

0.09

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,394,835  ·  11 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

0x5c8c6ab6…dc36

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x736c28d3…5d5a

0x065c9d…c394

3 touches
1 conflict

0x0f1c8d9e…d847

0x065c9d…c394

3 touches
1 conflict

0x1c601885…a733

0x065c9d…c394

3 touches
1 conflict

0x26932743…e11e

0x065c9d…c394

3 touches
1 conflict

0xbf04f37d…85f2

0x2a68ba…90c5

2 touches
0 conflicts

0x00000000…0002

0x7e9d3a…9fda

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 0x5c8c6ab6f0…86dc36

← previous block·next block →recent activity