Block #72,371,188

← previous blocknext block →recent activity

Analyzing

Block #72,371,188

5 transactions · 4 stateful · 2026-05-04 11:55:08 UTC

Parallelism

60/100

Blocked

25%

Avg conflicts / tx

0.2

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,371,188  ·  5 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

0x0c4875d8…0814

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x35521037…edf4

0x065c9d…c394

3 touches
1 conflict

0xf1edc7f4…7e63

0x065c9d…c394

3 touches
1 conflict

0xd585e071…d9e8

0x065c9d…c394

2 touches
0 conflicts

0xe60e6a14…f406

0x065c9d…c394

2 touches
0 conflicts

0xe6e91a85…94b8

0x065c9d…c394

2 touches
0 conflicts

0xf0b9e18d…eac7

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 0x0c4875d8af…9c0814

← previous block·next block →recent activity