Block #72,221,400

← previous blocknext block →recent activity

Analyzing

Block #72,221,400

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

Parallelism

67/100

Blocked

17%

Avg conflicts / tx

0.17

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,221,400  ·  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

0x2eba889b…45e3

0x065c9d…c394

4 touches
1 conflict

0x47b807a2…3307

0x065c9d…c394

4 touches
1 conflict

0x41755291…977f

0x065c9d…c394

2 touches
0 conflicts

0x44a6edf2…0dde

0x065c9d…c394

2 touches
0 conflicts

0x9f56afc7…418b

0x065c9d…c394

2 touches
0 conflicts

0xa9838c09…7ecd

0x065c9d…c394

2 touches
0 conflicts

0xea7f2e45…f6f2

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