← previous blocknext block →recent activity

Analyzing

Block #73,670,950

9 transactions · 8 stateful · 2026-05-10 12:12:25 UTC

Parallelism

78/100

Blocked

13%

Avg conflicts / tx

0.11

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,670,950  ·  9 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

0x1c309b87…bdc5

0x065c9d…c394

4 touches
1 conflict

0xcbc8fdca…b45b

0x065c9d…c394

3 touches
1 conflict

0xed7e8af3…46c0

0x065c9d…c394

3 touches
1 conflict

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x0ac31945…2c72

0x065c9d…c394

2 touches
0 conflicts

0x529acb6a…fcc6

0x065c9d…c394

2 touches
0 conflicts

0x7727b646…f20b

0x065c9d…c394

2 touches
0 conflicts

0xb7227bcf…d797

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 0x1c309b877c…f1bdc5

← previous block·next block →recent activity