← previous blocknext block →recent activity

Analyzing

Block #72,370,639

20 transactions · 16 stateful · 2026-05-04 11:51:29 UTC

Parallelism

65/100

Blocked

50%

Avg conflicts / tx

1.3

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #72,370,639  ·  20 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

0x9e689103…3332

0xd32edf…ff58

13 touches
21 conflicts

0xc3c8642a…7da5

0x2a68ba…90c5

8 touches
6 conflicts

0x17606ba6…1b6e

0x754704…b603

6 touches
3 conflicts

0xa1087a5c…66c4

0x754704…b603

6 touches
3 conflicts

0x561aa74b…c05a

0x065c9d…c394

5 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

4 touches
1 conflict

0x18b33b3b…197f

0x065c9d…c394

4 touches
1 conflict

0x00000000…0012

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

21 conflicts on slot 0x9e689103ca…e73332

← previous block·next block →recent activity