Block #72,225,346

← previous blocknext block →recent activity

Analyzing

Block #72,225,346

7 transactions · 5 stateful · 2026-05-03 19:39:27 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,225,346  ·  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

0x41755291…977f

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x04a8f1df…9eb5

0x065c9d…c394

3 touches
1 conflict

0x2746a602…e1fc

0x065c9d…c394

2 touches
0 conflicts

0x298bcc29…3960

0x065c9d…c394

2 touches
0 conflicts

0x3542f402…91b6

0x065c9d…c394

2 touches
0 conflicts

0xf7f33781…b9e3

0x065c9d…c394

2 touches
0 conflicts

0x74e71984…ae90

0x2a68ba…90c5

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 0x4175529119…79977f

← previous block·next block →recent activity