← previous blocknext block →recent activity

Analyzing

Block #72,233,733

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

Parallelism

71/100

Blocked

50%

Avg conflicts / tx

0.29

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #72,233,733  ·  17 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

0x134a140e…eee5

0xd32edf…ff58

5 touches
3 conflicts

0xd53220ed…473b

0x1b6862…e19c

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x00000000…0013

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x74e71984…ae90

0x2a68ba…90c5

4 touches
1 conflict

0x34d3f718…7c9d

0x065c9d…c394

3 touches
1 conflict

0xad828050…ba79

0xa6afd3…d132

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

3 conflicts on slot 0x134a140ee7…72eee5

← previous block·next block →recent activity