Block #72,172,482

← previous blocknext block →recent activity

Analyzing

Block #72,172,482

6 transactions · 5 stateful · 2026-05-03 13:44:19 UTC

Parallelism

67/100

Blocked

20%

Avg conflicts / tx

0.17

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,172,482  ·  6 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

0xffe431af…8faa

0x065c9d…c394

4 touches
1 conflict

0x26c15f2e…65c9

0x065c9d…c394

4 touches
1 conflict

0x5c8c6ab6…dc36

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x4c93193c…f061

0x065c9d…c394

2 touches
0 conflicts

0x8d53acc0…1cab

0x065c9d…c394

2 touches
0 conflicts

0xa096989b…7798

0x065c9d…c394

2 touches
0 conflicts

0xcc8ecd5b…432f

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 0xffe431af56…838faa

← previous block·next block →recent activity