Block #72,221,430

← previous blocknext block →recent activity

Analyzing

Block #72,221,430

6 transactions · 5 stateful · 2026-05-03 19:13:15 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,221,430  ·  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

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x6d3fcb1a…a6e4

0x065c9d…c394

4 touches
1 conflict

0x7d4a6a6e…5dbb

0x065c9d…c394

4 touches
1 conflict

0x0e78f269…4091

0x065c9d…c394

3 touches
1 conflict

0xf5d8e4d5…2cdb

0x065c9d…c394

3 touches
1 conflict

0x4341432b…ad29

0x065c9d…c394

2 touches
0 conflicts

0x7e803876…7d2f

0x065c9d…c394

2 touches
0 conflicts

0x9f56afc7…418b

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