Block #72,288,144

← previous blocknext block →recent activity

Analyzing

Block #72,288,144

18 transactions · 12 stateful · 2026-05-04 02:41:34 UTC

Parallelism

61/100

Blocked

50%

Avg conflicts / tx

1.17

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #72,288,144  ·  18 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x6a89ada1…efb3

0xd32edf…ff58

13 touches
21 conflicts

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x14d1bf0e…e099

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0013

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0018

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…0028

0x1b6862…e19c

2 touches
0 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

2 touches
0 conflicts

0x09000000…0001

0x000000…1000

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: 0xd32edf66…9fff58

21 conflicts on slot 0x6a89ada1c5…cfefb3

← previous block·next block →recent activity