Block #72,233,411

← previous blocknext block →recent activity

Analyzing

Block #72,233,411

7 transactions · 5 stateful · 2026-05-03 20:33:42 UTC

Parallelism

71/100

Blocked

20%

Avg conflicts / tx

0.14

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,233,411  ·  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

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xa02838a3…bc54

0x34b655…2a6f

4 touches
1 conflict

0xb18dd097…f409

0x34b655…2a6f

4 touches
1 conflict

0x04696edd…e403

0x065c9d…c394

2 touches
0 conflicts

0x41755291…977f

0x065c9d…c394

2 touches
0 conflicts

0x798531a9…eba1

0x065c9d…c394

2 touches
0 conflicts

0xd963c2f2…6a34

0x065c9d…c394

2 touches
0 conflicts

0xf0493190…b20b

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: 0x34b6552d…112a6f

1 conflict on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity