Block #72,855,866

← previous blocknext block →recent activity

Analyzing

Block #72,855,866

19 transactions · 15 stateful · 2026-05-06 17:45:14 UTC

Parallelism

63/100

Blocked

53%

Avg conflicts / tx

1.26

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #72,855,866  ·  19 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

0x2d8cacea…6571

0xd32edf…ff58

13 touches
21 conflicts

0x70b2f813…783c

0x2a68ba…90c5

6 touches
3 conflicts

0xa1087a5c…66c4

0x754704…b603

6 touches
3 conflicts

0x29f1c087…6a36

0x065c9d…c394

6 touches
3 conflicts

0x0f94ee4c…189b

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0013

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x46cb45de…a568

0x188d58…ea8e

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

21 conflicts on slot 0x2d8caceab6…7b6571

← previous block·next block →recent activity