← previous blocknext block →recent activity

Analyzing

Block #73,261,489

5 transactions · 5 stateful · 2026-05-08 14:44:15 UTC

Parallelism

60/100

Blocked

20%

Avg conflicts / tx

0.2

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,261,489  ·  5 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

0x6d0c65d9…c36f

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x578e7f66…1b56

0x34b655…2a6f

4 touches
1 conflict

0x0a2250a8…3cb1

0x34b655…2a6f

2 touches
0 conflicts

0x1b9e654e…0a08

0x34b655…2a6f

2 touches
0 conflicts

0x5dc14a96…6816

0x34b655…2a6f

2 touches
0 conflicts

0xfac43f12…b842

0x34b655…2a6f

2 touches
0 conflicts

0x09106a95…1467

0xeedfbc…f7dc

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: 0x34b6552d…112a6f

1 conflict on slot 0x6d0c65d93b…f1c36f

← previous block·next block →recent activity