Block #72,498,485

← previous blocknext block →recent activity

Analyzing

Block #72,498,485

9 transactions · 8 stateful · 2026-05-05 02:03:10 UTC

Parallelism

78/100

Blocked

13%

Avg conflicts / tx

0.11

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,498,485  ·  9 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

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xeedb7e85…ec3b

0x065c9d…c394

4 touches
1 conflict

0x83194eb1…b354

0x065c9d…c394

3 touches
1 conflict

0x4adb54da…112d

0x065c9d…c394

3 touches
1 conflict

0x5c8c6ab6…dc36

0x065c9d…c394

2 touches
0 conflicts

0x81fd68b0…3589

0x065c9d…c394

2 touches
0 conflicts

0x9999108f…b1a9

0x065c9d…c394

2 touches
0 conflicts

0xbb7625f0…29b5

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 0x0000000000…00003d

← previous block·next block →recent activity