← previous blocknext block →recent activity

Analyzing

Block #72,425,512

9 transactions · 7 stateful · 2026-05-04 17:57:14 UTC

Parallelism

78/100

Blocked

29%

Avg conflicts / tx

0.22

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,425,512  ·  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

0xd0f6f4f2…dffa

0x34b655…2a6f

4 touches
1 conflict

0x13fb143f…8415

0x065c9d…c394

4 touches
1 conflict

0xdf4bab7c…a2f6

0x065c9d…c394

3 touches
1 conflict

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x1a506558…f645

0x065c9d…c394

2 touches
0 conflicts

0x58fbf623…0e80

0x065c9d…c394

2 touches
0 conflicts

0x5c8c6ab6…dc36

0x065c9d…c394

2 touches
0 conflicts

0x6518c685…7c09

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: 0x34b6552d…112a6f

1 conflict on slot 0xd0f6f4f225…4cdffa

← previous block·next block →recent activity