← previous blocknext block →recent activity

Analyzing

Block #73,657,800

13 transactions · 9 stateful · 2026-05-10 10:43:46 UTC

Parallelism

85/100

Blocked

11%

Avg conflicts / tx

0.08

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,657,800  ·  13 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

0xed57bddf…1abf

0xc8689a…ee79

4 touches
1 conflict

0x0175b7a6…1dba

0x6c4bfa…a540

4 touches
1 conflict

0x0175b7a6…1dbb

0x6c4bfa…a540

4 touches
1 conflict

0x0175b7a6…1dbc

0x6c4bfa…a540

4 touches
1 conflict

0x0175b7a6…1dbd

0x6c4bfa…a540

4 touches
1 conflict

0x0c89ea7e…13eb

0x6c4bfa…a540

4 touches
1 conflict

0x0ef1e663…8f2a

0x6c4bfa…a540

4 touches
1 conflict

0x2e2214a9…fe0d

0x6c4bfa…a540

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