← previous blocknext block →recent activity

Analyzing

Block #72,571,569

7 transactions · 5 stateful · 2026-05-05 10:09:45 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,571,569  ·  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

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x43ec339a…7688

0x065c9d…c394

4 touches
1 conflict

0x4842d837…d01f

0x065c9d…c394

3 touches
1 conflict

0xcfcb0c93…b9b4

0x065c9d…c394

3 touches
1 conflict

0xcd0ab720…3d66

0x065c9d…c394

2 touches
0 conflicts

0xce06004c…7b14

0x065c9d…c394

2 touches
0 conflicts

0xcf9df718…9daa

0x065c9d…c394

2 touches
0 conflicts

0xfd1ca2ba…c72c

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