Block #72,283,198

← previous blocknext block →recent activity

Analyzing

Block #72,283,198

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

Parallelism

71/100

Blocked

25%

Avg conflicts / tx

0.43

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #72,283,198  ·  14 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

0x640d4e07…5b9f

0xd32edf…ff58

7 touches
6 conflicts

0x00000000…0013

0x1b6862…e19c

4 touches
1 conflict

0x8b41ec8f…c2d3

0x1b6862…e19c

4 touches
1 conflict

0x7def6cd3…f3fe

0x065c9d…c394

4 touches
1 conflict

0xbf04f37d…85f2

0x2a68ba…90c5

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0004

0x094452…0a09

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

6 conflicts on slot 0x640d4e0745…675b9f

← previous block·next block →recent activity