← previous blocknext block →recent activity

Analyzing

Block #73,048,318

24 transactions · 14 stateful · 2026-05-07 15:06:10 UTC

Parallelism

83/100

Blocked

29%

Avg conflicts / tx

0.29

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,048,318  ·  24 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

0x7f189cf6…afab

0x065c9d…c394

6 touches
3 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0x00000000…0002

0xab3526…fa38

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x9e0fbf38…ea4f

0x065c9d…c394

3 touches
1 conflict

0x24050120…76cf

0x065c9d…c394

3 touches
1 conflict

0xb47e1014…9136

0x065c9d…c394

3 touches
1 conflict

0x32c16512…2572

0x065c9d…c394

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: 0x065c9d28…a9c394

3 conflicts on slot 0x7f189cf621…beafab

← previous block·next block →recent activity