← previous blocknext block →recent activity

Analyzing

Block #72,233,731

15 transactions · 15 stateful · 2026-05-03 20:35:51 UTC

Parallelism

60/100

Blocked

53%

Avg conflicts / tx

1.2

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #72,233,731  ·  15 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x1e5ee1e2…e3fb

0xd32edf…ff58

11 touches
15 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x47b807a2…3307

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xbc32b88d…a918

0x065c9d…c394

3 touches
1 conflict

0x00000000…0000

0x63e48b…53f2

2 touches
0 conflicts

0x09000000…0001

0x000000…1000

2 touches
0 conflicts

0x00000000…0004

0x63e48b…53f2

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

15 conflicts on slot 0x1e5ee1e2d0…72e3fb

← previous block·next block →recent activity