← previous blocknext block →recent activity

Analyzing

Block #72,498,704

20 transactions · 13 stateful · 2026-05-05 02:04:38 UTC

Parallelism

75/100

Blocked

38%

Avg conflicts / tx

0.4

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #72,498,704  ·  20 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x5c8c6ab6…dc36

0x065c9d…c394

6 touches
3 conflicts

0xd8a4fa1c…ad8a

0xd32edf…ff58

5 touches
3 conflicts

0x74e71984…ae90

0x2a68ba…90c5

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x68a1526e…9461

0x065c9d…c394

4 touches
1 conflict

0x2561ecc8…7d99

0x065c9d…c394

3 touches
1 conflict

0x2561ecc8…7d9a

0x065c9d…c394

3 touches
1 conflict

0xaae2db77…62b0

0x065c9d…c394

3 touches
1 conflict

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

3 conflicts on slot 0x5c8c6ab6f0…86dc36

← previous block·next block →recent activity