Block #72,314,956

← previous blocknext block →recent activity

Analyzing

Block #72,314,956

10 transactions · 9 stateful · 2026-05-04 05:40:35 UTC

Parallelism

60/100

Blocked

33%

Avg conflicts / tx

0.4

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #72,314,956  ·  10 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x7d8474b3…351f

0x065c9d…c394

6 touches
3 conflicts

0x438cf5f6…f077

0x2a68ba…90c5

6 touches
3 conflicts

0x11b69a7e…334e

0xee8c0e…1242

4 touches
1 conflict

0x4aae89e8…3e82

0x2a68ba…90c5

4 touches
1 conflict

0x8876d94c…8435

0x2a68ba…90c5

4 touches
1 conflict

0xba3d2100…4266

0x2a68ba…90c5

4 touches
1 conflict

0x536c1c5f…ce14

0xa6afd3…d132

4 touches
1 conflict

0xa5c7bab1…2716

0xd32edf…ff58

3 touches
1 conflict

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 0x7d8474b370…39351f

← previous block·next block →recent activity