← previous blocknext block →recent activity

Analyzing

Block #73,495,598

17 transactions · 11 stateful · 2026-05-09 16:42:03 UTC

Parallelism

82/100

Blocked

27%

Avg conflicts / tx

0.24

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,495,598  ·  17 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

0x1bc9b1ca…85ef

0x34b655…2a6f

6 touches
3 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0x9ef1c4f8…479e

0x34b655…2a6f

6 touches
3 conflicts

0xafd59af5…5257

0xc8689a…ee79

4 touches
1 conflict

0xbaa67d76…5cdc

0x34b655…2a6f

4 touches
1 conflict

0xbd64801a…6689

0x34b655…2a6f

4 touches
1 conflict

0xffedaa84…311b

0x34b655…2a6f

4 touches
1 conflict

0x0d622e34…0000

0x681e90…ae09

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

3 conflicts on slot 0x1bc9b1cade…5085ef

← previous block·next block →recent activity