Block #73,648,262

← previous blocknext block →recent activity

Analyzing

Block #73,648,262

15 transactions · 12 stateful · 2026-05-10 09:39:28 UTC

Parallelism

47/100

Blocked

67%

Avg conflicts / tx

1.93

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #73,648,262  ·  15 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0xfc91f0eb…fb6c

0xd32edf…ff58

15 touches
28 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0xa949ad3e…395b

0x065c9d…c394

4 touches
1 conflict

0x00000000…0012

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0013

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x00000000…001b

0x1b6862…e19c

4 touches
1 conflict

0x00000000…002b

0x1b6862…e19c

4 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: 0xd32edf66…9fff58

28 conflicts on slot 0xfc91f0ebe5…99fb6c

← previous block·next block →recent activity