← previous blocknext block →recent activity

Analyzing

Block #73,482,564

10 transactions · 9 stateful · 2026-05-09 15:15:17 UTC

Parallelism

60/100

Blocked

44%

Avg conflicts / tx

0.7

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,482,564  ·  10 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

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0x8c913118…1aa1

0x065c9d…c394

4 touches
1 conflict

0x6ddd19f5…f8f0

0x065c9d…c394

4 touches
1 conflict

0xf537eaa0…73c8

0x065c9d…c394

4 touches
1 conflict

0x7234c38a…e685

0x065c9d…c394

4 touches
1 conflict

0xe2926dfb…efa4

0x065c9d…c394

3 touches
1 conflict

0x8fb036ee…e34a

0x065c9d…c394

3 touches
1 conflict

0x9297fbd1…efd4

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

3 conflicts on slot 0x046a928e85…e50012

← previous block·next block →recent activity