Block #72,283,868

← previous blocknext block →recent activity

Analyzing

Block #72,283,868

12 transactions · 9 stateful · 2026-05-04 02:12:48 UTC

Parallelism

83/100

Blocked

11%

Avg conflicts / tx

0.08

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,283,868  ·  12 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

0xf08dab4a…7d77

0x065c9d…c394

3 touches
1 conflict

0x2b2c3c54…4a6d

0x065c9d…c394

3 touches
1 conflict

0x95155655…efd0

0x065c9d…c394

3 touches
1 conflict

0x5b4152ac…255f

0x065c9d…c394

2 touches
0 conflicts

0x74e71984…ae90

0x2a68ba…90c5

2 touches
0 conflicts

0xb1acfe51…c6b1

0x3bd359…433a

2 touches
0 conflicts

0xf6cc7de8…0b4a

0x3bd359…433a

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