← previous blocknext block →recent activity

Analyzing

Block #73,987,468

7 transactions · 6 stateful · 2026-05-11 23:32:55 UTC

Parallelism

71/100

Blocked

17%

Avg conflicts / tx

0.14

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,987,468  ·  7 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x05eea3e3…5846

0x2a68ba…90c5

4 touches
1 conflict

0xa67e4000…e125

0x065c9d…c394

3 touches
1 conflict

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x5e562d35…1124

0x065c9d…c394

2 touches
0 conflicts

0x6b0c2e83…418b

0x065c9d…c394

2 touches
0 conflicts

0xe49532bc…65fd

0x065c9d…c394

2 touches
0 conflicts

0x00000000…0012

0x1b6862…e19c

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: 0x2a68ba18…8e90c5

1 conflict on slot 0x05eea3e32f…c95846

← previous block·next block →recent activity