Block #73,210,520

← previous blocknext block →recent activity

Analyzing

Block #73,210,520

10 transactions · 9 stateful · 2026-05-08 09:05:22 UTC

Parallelism

50/100

Blocked

44%

Avg conflicts / tx

0.7

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,210,520  ·  10 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0xce7bfe5e…5e58

0x065c9d…c394

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xb78c653b…d463

0x065c9d…c394

4 touches
1 conflict

0x01d0a492…3e9d

0x065c9d…c394

4 touches
1 conflict

0x290279f5…e504

0x065c9d…c394

3 touches
1 conflict

0x200e1edd…bc96

0x065c9d…c394

3 touches
1 conflict

0x44f1b90b…2c1d

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 0xf2f76ab392…f3623e

← previous block·next block →recent activity