Block #72,314,642

← previous blocknext block →recent activity

Analyzing

Block #72,314,642

7 transactions · 4 stateful · 2026-05-04 05:38:29 UTC

Parallelism

71/100

Blocked

25%

Avg conflicts / tx

0.14

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,314,642  ·  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

0x11b80e55…6142

0x065c9d…c394

4 touches
1 conflict

0xbcf25234…e4be

0x065c9d…c394

3 touches
1 conflict

0x5d1820c5…4c25

0x065c9d…c394

3 touches
1 conflict

0x24968e6d…0132

0x065c9d…c394

2 touches
0 conflicts

0x7093e616…af2c

0x065c9d…c394

2 touches
0 conflicts

0xa487b942…3ee3

0x065c9d…c394

2 touches
0 conflicts

0xc30c932f…8731

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