← previous blocknext block →recent activity

Analyzing

Block #72,395,173

21 transactions · 17 stateful · 2026-05-04 14:35:02 UTC

Parallelism

76/100

Blocked

47%

Avg conflicts / tx

0.81

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #72,395,173  ·  21 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x00000000…003d

0x065c9d…c394

10 touches
10 conflicts

0x5c8c6ab6…dc36

0x065c9d…c394

8 touches
6 conflicts

0xadac4a86…c2bc

0x34b655…2a6f

6 touches
3 conflicts

0xf724e01e…46b9

0xd32edf…ff58

5 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

4 touches
1 conflict

0x6882a8f0…0212

0x065c9d…c394

4 touches
1 conflict

0xdcc3aeda…1cb0

0x065c9d…c394

4 touches
1 conflict

0x91220b8f…7a03

0x1b6862…e19c

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

10 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity