Block #72,430,019

← previous blocknext block →recent activity

Analyzing

Block #72,430,019

6 transactions · 5 stateful · 2026-05-04 18:27:12 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,430,019  ·  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

0x8f375dda…1b11

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x36075cb1…467e

0x065c9d…c394

2 touches
0 conflicts

0x90c65156…8a66

0x065c9d…c394

2 touches
0 conflicts

0xdda897b6…b0a8

0x065c9d…c394

2 touches
0 conflicts

0xe409b830…4ba3

0x065c9d…c394

2 touches
0 conflicts

0x2aab0897…78f7

0x34b655…2a6f

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: 0x34b6552d…112a6f

1 conflict on slot 0x8f375dda91…3c1b11

← previous block·next block →recent activity