← previous blocknext block →recent activity

Analyzing

Block #72,496,389

10 transactions · 9 stateful · 2026-05-05 01:49:13 UTC

Parallelism

80/100

Blocked

11%

Avg conflicts / tx

0.1

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,496,389  ·  10 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

0xf0aeb96a…ebca

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x45067b40…9a69

0x065c9d…c394

4 touches
1 conflict

0x8e6de25e…72e9

0x065c9d…c394

3 touches
1 conflict

0xa18321bc…c582

0x065c9d…c394

3 touches
1 conflict

0x097ac333…27f2

0x065c9d…c394

3 touches
1 conflict

0x33b19b24…0b55

0x065c9d…c394

2 touches
0 conflicts

0x3cd91bc3…061f

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 0xf0aeb96ade…e0ebca

← previous block·next block →recent activity