← previous blocknext block →recent activity

Analyzing

Block #73,484,003

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

Parallelism

80/100

Blocked

11%

Avg conflicts / tx

0.1

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,484,003  ·  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

0x6f08361d…bda6

0x065c9d…c394

4 touches
1 conflict

0xd9f0eea0…a9c3

0x065c9d…c394

4 touches
1 conflict

0xf537eaa0…73c8

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x4f47bf07…02c0

0x065c9d…c394

2 touches
0 conflicts

0xc8402ce0…01ff

0x065c9d…c394

2 touches
0 conflicts

0xd4cb5162…e632

0x065c9d…c394

2 touches
0 conflicts

0xf63faf85…4eb4

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 0x6f08361da9…89bda6

← previous block·next block →recent activity