Block #72,283,184

← previous blocknext block →recent activity

Analyzing

Block #72,283,184

8 transactions · 8 stateful · 2026-05-04 02:08:12 UTC

Parallelism

63/100

Blocked

25%

Avg conflicts / tx

0.38

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #72,283,184  ·  8 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x24968e6d…0132

0x065c9d…c394

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x2b2c3c54…4a6d

0x065c9d…c394

2 touches
0 conflicts

0x5b4152ac…255f

0x065c9d…c394

2 touches
0 conflicts

0x6e0dc6a1…2922

0x065c9d…c394

2 touches
0 conflicts

0xdd045c65…a68b

0x065c9d…c394

2 touches
0 conflicts

0xf08dab4a…7d77

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

3 conflicts on slot 0x24968e6db4…f00132

← previous block·next block →recent activity