Block #73,681,651

← previous blocknext block →recent activity

Analyzing

Block #73,681,651

16 transactions · 12 stateful · 2026-05-10 13:24:48 UTC

Parallelism

69/100

Blocked

33%

Avg conflicts / tx

0.5

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,681,651  ·  16 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

0x046a928e…0012

0x2a68ba…90c5

8 touches
6 conflicts

0x529acb6a…fcc6

0x065c9d…c394

4 touches
1 conflict

0xa1476eab…edfc

0xd32edf…ff58

3 touches
1 conflict

0xcaeed173…b7ea

0x065c9d…c394

2 touches
0 conflicts

0x5d82c9b5…004c

0x3bd359…433a

2 touches
0 conflicts

0xfe3bddd2…8b48

0x3bd359…433a

2 touches
0 conflicts

0x00000000…0003

0x5afd3e…7620

2 touches
0 conflicts

0x00000000…0004

0x5afd3e…7620

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

6 conflicts on slot 0x046a928e85…e50012

← previous block·next block →recent activity