Block #72,225,116

← previous blocknext block →recent activity

Analyzing

Block #72,225,116

7 transactions · 4 stateful · 2026-05-03 19:37:53 UTC

Parallelism

71/100

Blocked

25%

Avg conflicts / tx

0.14

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,225,116  ·  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

0x8ad5464a…41cf

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x7985f274…c5bd

0x065c9d…c394

3 touches
1 conflict

0xfb5024fd…99b4

0x065c9d…c394

3 touches
1 conflict

0x02d2adff…e661

0x065c9d…c394

2 touches
0 conflicts

0x3610ec01…67b9

0x065c9d…c394

2 touches
0 conflicts

0x9ba6b0ba…a273

0x065c9d…c394

2 touches
0 conflicts

0xc744f3e4…e5b1

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 0x8ad5464a09…5041cf

← previous block·next block →recent activity