Block #73,470,198

← previous blocknext block →recent activity

Analyzing

Block #73,470,198

10 transactions · 7 stateful · 2026-05-09 13:53:04 UTC

Parallelism

80/100

Blocked

14%

Avg conflicts / tx

0.1

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,470,198  ·  10 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

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xc18c28de…78c0

0x065c9d…c394

3 touches
1 conflict

0xea953b66…a60d

0x065c9d…c394

3 touches
1 conflict

0x178df194…bd91

0x065c9d…c394

2 touches
0 conflicts

0x200f6666…c57d

0x065c9d…c394

2 touches
0 conflicts

0x2fc4c995…41aa

0x065c9d…c394

2 touches
0 conflicts

0x6f08361d…bda6

0x065c9d…c394

2 touches
0 conflicts

0x81f0311c…7592

0x065c9d…c394

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: 0x065c9d28…a9c394

1 conflict on slot 0x0000000000…00003d

← previous block·next block →recent activity