← previous blocknext block →recent activity

Analyzing

Block #72,284,180

8 transactions · 7 stateful · 2026-05-04 02:14:54 UTC

Parallelism

50/100

Blocked

43%

Avg conflicts / tx

0.63

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #72,284,180  ·  8 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x24968e6d…0132

0x065c9d…c394

6 touches
3 conflicts

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x09075329…ea22

0x065c9d…c394

4 touches
1 conflict

0xe5275a11…fbea

0x065c9d…c394

3 touches
1 conflict

0xe227487a…29c5

0x065c9d…c394

3 touches
1 conflict

0xaeedb480…ff7c

0x065c9d…c394

3 touches
1 conflict

0xb321fbf2…aac1

0x065c9d…c394

3 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

3 conflicts on slot 0x24968e6db4…f00132

← previous block·next block →recent activity