← previous blocknext block →recent activity

Analyzing

Block #73,698,490

11 transactions · 8 stateful · 2026-05-10 15:18:16 UTC

Parallelism

73/100

Blocked

38%

Avg conflicts / tx

0.36

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,698,490  ·  11 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xed57bddf…1abf

0xc8689a…ee79

4 touches
1 conflict

0x0175b7a6…1dba

0x6c4bfa…a540

4 touches
1 conflict

0x0175b7a6…1dbc

0x6c4bfa…a540

4 touches
1 conflict

0x0c89ea7e…13eb

0x6c4bfa…a540

4 touches
1 conflict

0x1a4b4152…0a08

0x6c4bfa…a540

4 touches
1 conflict

0xf0f673fd…37a7

0x6c4bfa…a540

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x0ac31945…2c72

0x065c9d…c394

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: 0xc8689a47…62ee79

1 conflict on slot 0xed57bddf8e…bd1abf

← previous block·next block →recent activity