Block #72,296,299

← previous blocknext block →recent activity

Analyzing

Block #72,296,299

24 transactions · 18 stateful · 2026-05-04 03:36:18 UTC

Parallelism

83/100

Blocked

33%

Avg conflicts / tx

0.54

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #72,296,299  ·  24 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

0x56f04bf3…c096

0x065c9d…c394

7 touches
6 conflicts

0x185df9e5…d799

0xd32edf…ff58

7 touches
6 conflicts

0xc3c8642a…7da5

0x2a68ba…90c5

6 touches
3 conflicts

0xa1087a5c…66c4

0x754704…b603

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x9a555477…19a8

0x754704…b603

4 touches
1 conflict

0x00000000…0004

0x63e48b…53f2

4 touches
1 conflict

0xf6cc7de8…0b4a

0x3bd359…433a

4 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

6 conflicts on slot 0x56f04bf35f…28c096

← previous block·next block →recent activity